[ << ]
[ < ]
[ Home ]
[ > ]
[ >> ]
8. Frequently Asked Questions
Content:
8.a. I get "configure: error: C compiler cannot create executables"
This is a generic error and can be caused by just about anything. The test is
pretty simple: can the requested compiler create an executable? However, this
relies on many things being correct: the toolchain itself being completely
sane, the compiler and compiler flags being appropriate, your environment set
up properly, etc... The only way to find out the real source of the problem is
to open up the generated config.log file and scroll down to where
this test is run and see what exactly the error message is that the toolchain
is spitting out.
8.b. "epatch" always fails in newly compiled system
The bash package does not properly cross-compile and mixes the host signal
definitions with those of the target. This manifests itself differently
depending on the combination of host architecture and target architecture. To
resolve the issue, simply re-compile bash natively. "But bash uses epatch!"
you exclaim. In that case, you will need to modify the ebuild and comment out
all the calls to epatch. Once you've installed the fixed bash this way,
uncomment all of the bash lines and rebuild it again.
8.c. uClibc build segfaults/crashes while building locale
The uClibc locale support is pretty experimental at this point. Unless you
really need support for it (and you're willing to help bang on the problem),
simply disable support by adding -nls -iconv -pregen -userlocales to
your USE when building uClibc.
[ << ]
[ < ]
[ Home ]
[ > ]
[ >> ]
The contents of this document are licensed under the Creative Commons -
Attribution / Share Alike license.
|