On Wednesday 01 November 2006 08:20, Luca wrote:
> 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).

Sorry for my barging into your talking but it seems I can suggest
something helpful.

1. First, some philosophy. Luca, if you _know_ the settings are correct
   then you also know what the error is. But you do _not_ know what the
   error is, so you don't know whether you settings are correct.

   The best way to prove they are so or to find the error in them is
   sending the output of the "set" command (is you use bash) showing
   all the environment variables and their values, to this list.

2. Try to reproduce the error. You saw it appeared when configure tried
   to execute "cc conftest.c". Create the file in the directory where
   it was created when ./configuring, like that one described by you
   above (that one from config.log), try to compile it with that
   command and send here the command output.

3. Are you sure you use "--build=${CLFS_HOST} --host=${CLFS_TARGET}"
   configure flags?

-- 
Nothing but perfection
pv
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support

Reply via email to