path: root/docs
diff options
authorYann E. MORIN" <>2010-07-22 21:33:17 (GMT)
committerYann E. MORIN" <>2010-07-22 21:33:17 (GMT)
commita8fa17de9f24f6a2f05e6e1cb23a2ffb5100b0e5 (patch)
tree9cec19ca8e78a0f72a3680ced5d8cbd2bd815c35 /docs
parent25bb99693ae8a9fe34693dac5b5046c8f36d42f2 (diff)
docs/known-issues: document the "error compiling FC test program" issue
Diffstat (limited to 'docs')
1 files changed, 22 insertions, 0 deletions
diff --git a/docs/known-issues.txt b/docs/known-issues.txt
index be7c3fa..95e1991 100644
--- a/docs/known-issues.txt
+++ b/docs/known-issues.txt
@@ -97,3 +97,25 @@ Workaround:
Build shared companion libraries.
+ While building the final gcc, I get an error message that ends with:
+ libtool.m4: error: problem compiling FC test program
+ The gc build procedure tries to run a Fortran test to see if it has a
+ working native fortran compiler installed on the build machine, and it
+ can't find one. A native Fortran compielr is needed (seems to be) to
+ build the Fortran frontend of the cross-compiler.
+ Even if you don't want to build the Fortran frontend, gcc tries to see
+ if it has one, but fails. This is no problem, as the Fortran frontend
+ will not be built. There is nothing to be worry about (unless you do
+ want to build the Fortran frontend, of course).
+ None so far. It's a spurious error, so there will probably never be
+ a fix for this issue.
+ None needed, it's a spurious error.