Hi again!
_Why_ are you afraid of sending the output of the "set" command here?
Here is mine, can I look at your one?
$ set |egrep '^(CC|LD|CLFS|PATH|MACHTYPE)'
CC=i686-pc-linux-gnu-gcc
CLFS=/mnt/clfs
CLFS_HOST=i686-cross-linux-gnu
CLFS_TARGET=i686-pc-linux-gnu
LD=i686-pc-linux-gnu-ld
MACHTYPE=i686-pc-linux-gnu
PATH=/cross-tools/bin:/usr/bin:/bin
Though... Hey!!!
I looked at the ./configure output given in one of your previous
letters and found something strange (CLFS editors, please correct me if
I'm wrong).
> configure: loading cache ./config.cache
> checking for a BSD-compatible install... /tools/install
> checking whether build environment is sane... yes
Why /tools/install? The system in /tools is to help you building the
base system _when being run on the target architecture_ while the whole
ch6. has to be built from the host. In other words, your path is set so
that you use binaries for running on the target system to be run on
the host one. It could even be not possible to run it at all.
Why ./config.cache? It doesn't seem to be mentioned in the CLFS book.
> configure: Doing configure of native tools (i686-pc-linux-gnu).
> checking for a BSD-compatible install... /tools.cross/install
> checking whether build environment is sane... yes
What's /tools.cross/install? In my case the found install was
/usr/bin/install (neither /cross-tools/bin/install nor
/tools/bin/install) since /cross-tools don't have install at all.
When building the temporary system /usr/bin/install is used. When
building the base system /tools/bin/install is used.
P.S. I begin to understand why you don't send us the "set" output.
Nevertheless, please tell us what are you doing and we'll try to
help you.
--
Nothing but perfection
pv
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
