Am 22.06.2016 um 18:35 schrieb Pierre Labastie:
Did you type the CC=... CXX=... etc lines? They are needed (with
backslash as continuation character) to get the behavior I
described... Maybe LFS_TGT is not set? Or $LFS_TGT-gcc is not found in
the PATH? To be clear, you can unpack gcc outside chroot and run
configure as you did (hopefully with the CC= etc lines), but as user
"lfs", and with the specific environment for that user.
Yes. As user lfs i did as the book says.
CC=$LFS_TGT-gcc \
CXX=$LFS_TGT-g++
...
Then compilation as indicated in the book:
../configure \ --prefix=/tools \ --with-local-prefix=/tools \
--with-native-system-header-dir=/tools/include \
--enable-languages=c,c++ \ --disable-libstdcxx-pch \ --disable-multilib
\ --disable-bootstrap \ --disable-libgomp
goes OK.
The mentioned line is "checking for gcc... gcc"
LFS_TGT was not set. I got on the corresponding command:
bash: `dirname $($LFS_TGT-gcc
-print-libgcc-file-name)`/include-fixed/limits.h: Permission denied
I anyway think that structures arent more clean now, after going from
root to lfs, no chroot, again lfs. I do not trust anymore.
I hope, the book can be changed to include 32 bit ;-)
Regards,
Edgar
--
Dr.-Ing. Edgar Alwers <[email protected]>
GPG Key ID:AD5C6F70
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style