Ken Moffat wrote: > On Tue, Oct 31, 2006 at 02:18:29PM +0100, Luca wrote: > >> Luca wrote: >> > * please * trim what you are replying to. Keeping some context is > * good. Sending 180 lines with a two-line reply wastes everybody's > * bandwidth. > > But, since I haven't yet replied to your previous post - > > >>> checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc >>> checking for C compiler default output file name... configure: error: C >>> compiler cannot create executables >>> See `config.log' for more details. >>> > ^^^^^^^^^^^^ > > Often, config.log is helpful. You will see the results of every > test that was run, followed by a dump of all the variables. So, > when configure fails you should start at the end of the log and > search back for the error message. > >> Temporary fixed the problem by commenting all the configure lines about >> the test if cross-compiling... >> > Conceivably, the configure script could have an error. But it's > far more likely that there is a real problem with your cross-compiler > (or the environment, e.g. CFLAGS). I'm assuming you haven't slipped > back to using the host compiler here, that will link against libs on > the host. > > ĸen > Hi Ken!
yeah, sorry to everyone about trimming... I checked and double-checked all the env and settings variables and everything's right, in fact all other packages when cross-compiling gave no errors, this one is the only that broke in this way (however it then checks for cross-compiling only to build some native tools before building the package). Luca _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
