On Jan 10, 2012, at 3:58 PM, Andrew Benton wrote:
> Fix this. Glibc does not like mawk. Use gawk.
> Also, can you please stop top posting and trim your replies to the
> relevant content?
Building binutils (pass 3?):
http://www.linuxfromscratch.org/lfs/view/stable/chapter06/binutils.html
It's hard to tell if my observations are related to the previous binutils posts
from the excessively long quoting...But, I've run into issues with both the
compilation and the testing. Specifically,
make tooldir=/usr
fails (looks like subdirs without Makefiles, or something like that):
config.status: creating po/Makefile.in
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default-1 commands
config.status: executing bfd_stdint.h commands
config.status: executing default commands
make[3]: Leaving directory `/sources/binutils-build/bfd/po'
make[3]: Entering directory `/sources/binutils-build/bfd/po'
make[3]: Nothing to be done for `info'.
make[3]: Leaving directory `/sources/binutils-build/bfd/po'
make[3]: Entering directory `/sources/binutils-build/bfd'
make[3]: Nothing to be done for `info-am'.
make[3]: Leaving directory `/sources/binutils-build/bfd'
make[2]: *** [info-recursive] Error 1
make[2]: Leaving directory `/sources/binutils-build/bfd'
make[1]: *** [all-bfd] Error 2
make[1]: Leaving directory `/sources/binutils-build'
make: *** [all] Error 2
Even if this is acceptable, it's rather disconcerting. Could a patch be made
to avoid descending into bfd, etc?
============
In addition, testing:
make -k check
also seems to fail, perhaps also due to empty subdirs (or something similar):
make[4]: Leaving directory `/sources/binutils-build/bfd'
make[3]: Leaving directory `/sources/binutils-build/bfd'
make[2]: Leaving directory `/sources/binutils-build/bfd'
/bin/sh: line 3: cd: ./opcodes: No such file or directory
make[1]: *** [check-opcodes] Error 1
/bin/sh: line 3: cd: ./binutils: No such file or directory
make[1]: *** [check-binutils] Error 1
/bin/sh: line 3: cd: ./etc: No such file or directory
make[1]: *** [check-etc] Error 1
/bin/sh: line 3: cd: ./gas: No such file or directory
make[1]: *** [check-gas] Error 1
/bin/sh: line 3: cd: ./gprof: No such file or directory
make[1]: *** [check-gprof] Error 1
make[2]: Entering directory `/sources/binutils-build/intl'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/sources/binutils-build/intl'
/bin/sh: line 3: cd: ./ld: No such file or directory
make[1]: *** [check-ld] Error 1
make[2]: Entering directory `/sources/binutils-build/libiberty'
make[3]: Entering directory `/sources/binutils-build/libiberty/testsuite'
gcc -DHAVE_CONFIG_H -g -O2 -I..
-I../../../binutils-2.21.1/libiberty/testsuite/../../include -o test-demangle \
../../../binutils-2.21.1/libiberty/testsuite/test-demangle.c
../libiberty.a
./test-demangle < ../../../binutils-2.21.1/libiberty/testsuite/demangle-expected
./test-demangle: 827 tests, 0 failures
gcc -DHAVE_CONFIG_H -g -O2 -I..
-I../../../binutils-2.21.1/libiberty/testsuite/../../include -DHAVE_CONFIG_H
-I.. -o test-pexecute \
../../../binutils-2.21.1/libiberty/testsuite/test-pexecute.c
../libiberty.a
./test-pexecute
gcc -DHAVE_CONFIG_H -g -O2 -I..
-I../../../binutils-2.21.1/libiberty/testsuite/../../include -DHAVE_CONFIG_H
-I.. -o test-expandargv \
../../../binutils-2.21.1/libiberty/testsuite/test-expandargv.c
../libiberty.a
./test-expandargv
PASS: test-expandargv-0.
PASS: test-expandargv-1.
PASS: test-expandargv-2.
PASS: test-expandargv-3.
PASS: test-expandargv-4.
PASS: test-expandargv-5.
PASS: test-expandargv-6.
make[3]: Leaving directory `/sources/binutils-build/libiberty/testsuite'
make[2]: Leaving directory `/sources/binutils-build/libiberty'
make[1]: Target `check-host' not remade because of errors.
make[1]: Nothing to be done for `check-target'.
make[1]: Leaving directory `/sources/binutils-build'
make: *** [do-check] Error 2
make: Target `check' not remade because of errors.
There are indications it's working. Something about 'test-demangle' passing
827 tests and failing 0 and later some PASS messages. But, when the book says:
"The test suite for Binutils in this section is considered critical. Do
not skip it under any circumstances."
and the testing fails it's unnerving.
======================================
I'm working under the assumption that the tests are succeeding, and that
descending the subdirs could be eliminated. It's possible that I'm somehow
compiling things incorrectly (though it's not my first trip around the LFS
block). It's also possible that the tests are actually failing, and somehow
it's just showing up now--which seems odd, since I'm no longer using the
"cross-compiled" toolchain, but rather the tools in /bin after the chroot-jail.
Anything jump out at anyone?
Q
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
