On Mon, 19 Sep 2005, Albert wrote:
LFS 6.1; chpt 6.13.1 Installation of Binutils; GoboLinux 012;
Here is the output from 'make check'. I can make no sense of it.
Any pointers appreciated.
I'm just catching up with my mail after a weekend away, but I think
I've seen several posts from you, and two things stick in my mind -
First, GoboLinux is probably one of the most unusual host distros you
can pick, which might mean it can generate difficulties of its own.
Second, you've not specified what processor you are running on.
root:/sources/binutils-build# make check
make[1]: Entering directory `/sources/binutils-build/bfd'
Making check in doc
make[2]: Entering directory `/sources/binutils-build/bfd/doc'
make[2]: Nothing to be done for `check'.
[ snipping the rest of this intro, I like a full log as much as the next
guy, but all this is absolutely normal stuff ]
WARNING: Couldn't find the global config file.
WARNING: Couldn't find tool init file
[ pretty normal so far ]
Test Run By root on Mon Sep 19 17:24:34 2005
Native configuration is i686-pc-linux-gnu
=== binutils tests ===
Schedule of variations:
unix
Running target unix
Using /tools/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /tools/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /sources/binutils-2.15.94.0.2.2/binutils/testsuite/config/default.exp
as tool-and-target-specific interface file.
file isfile ../gas/as-new: 1
Running
/sources/binutils-2.15.94.0.2.2/binutils/testsuite/binutils-all/ar.exp ...
FAIL: ar long file names
ERROR:
This failure might be a platform-specific failure, I've seen it
somewhere (x86_64 or ppc, probably)
/sources/binutils-2.15.94.0.2.2/binutils/testsuite/binutils-all/bintest.s:
assembly failed
ERROR:
/sources/binutils-2.15.94.0.2.2/binutils/testsuite/binutils-all/bintest.s:
assembly failed
Looks like something is seriously broken, assembly isn't supposed to
fail. A week ago I had a nightmare build where for some reason the
mounting didn't all work (it's scripted, and the failure to mount was
not reproducible). Possibly you have somewhat similar weirdness.
=== binutils Summary ===
# of expected passes 1
# of unexpected failures 1
That will be ar long file names - bad if this is i686
# of unresolved testcases 4
Those will be the assembly failures.
Something seems to be seriously wrong. For starters, check that /proc
and /sys are mounted (from inside chroot, a simple 'ls' will prove
if there is anything in these two directories). Also check for all the
device files from section 6.8.2.
Did you run the check for glibc without problems ?
Have you come back to the build after shutting down ?
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
