Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I see what you mean now.
The book is a little bit off
I have 1.3.3 as compile problem
I already rebuilt it after the last post
I made my own logfile based on your past sugestion 1> mylog 2>&1
Sorry I am not sure which buildlogs you ar refering to.
Are they created by make or make check or is this just mylog or whatever I create to capture the file as it's being built ?
I did not see any logfiles or buildlogs in /glibc-build except the config.log
BTW I forgot to answer the question about configure in my last post.
Yes the error with the "/dev/null" is still there right from the begining
but it continues past it and finishes with exit 0
I looked at that buildlog for 6.1.1 (chapter6 glibc 2.3.4) and it's pretty similar to mylog that was created with make -k check
I will try to copy it here and edit it for what my file looks like
That's actually one long line that wraps around
/sources/glibc-build/posix/wordexp-test.o(.text+0x402): In function `main':
/sources/glibc-2.3.4-20040701/posix/wordexp=test.c:249: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
Then another long line this is the only one that shows after running make check a second time after the first without rebuilding it
GCONV_PATH=/tools/build/glibc-build/iconvdata LC_ALL=C /sources/glibc-build/elf/ld-linux.so.2 --library-path /sources/glibc-build:/sources/glibc-build/math:
/sources/glibc-build/crypt:/sources/glibc-build/nptl /sources/glibc-build/posix/wordexp-test > /sources/glibc-build/posix/wordexp-test.out
Then the make check stops after the error
Here are the other errors from runing make check with the -k flag
From the top
make: *** [/sources/glibc-build/posix/wordxp-test.out] Error 1
make: *** [/sources/glibc-build/posix/annexc.out Error 1 (ignored)
make: *** [/posix/tests] Error 2
make: *** [/sources/glibc-build/nptl/tst-mutex8.out Error 127
The same error (Error 127) is repeated for tst-cond7.out,tst-cond8.out,
tst-once3.out, tst-once4.out, tst-key3.out
These 2 have (Error 1) tst-basic3.out, tst-basic4.out
Then more Error 127's all in the /sources/glibc-build/nptl directory
about 43 files
Then just a few more after that
make: *** [nptl/tests] Error 2
make: *** [/sources/glibc-build/rt/tst-mqueue8x.out] Error 127
make: *** [rt/tests] Error 2
make: *** [check] Error 2
I did a little experimenting and I seem to have stumbled upon a solution.
This may mean I have to deviate from the book at least just temporarily.
I know you said earlier
" The ramfs mount is done on top of the previous mounts (console/null), this would mean that ramfs is mounted on top of the previous /dev and the /dev/null and /dev/console entries are still there, but not visible/reachable. The udevstart command (command after mounting ramfs) should create the needed device nodes (on demand)."
But I was thinking for some reason during configure on the first line
when it's looking for /dev/null it doesn't see it or it's not "reachable"
So I left everything out of "populating dev"
I exited and reentered chroot (I did not reboot) and went straight into
Right away I noticed that I no longer had the error about the /dev/null
So after doing " make" I ran "make -k check" to a logfile and after examining it I noticed I no longer have the wordexp-test.out error but I still had all the other ones.
Then I ran "make check" without loging it and it went through to the end without errors.
So I figured I may as well go ahead and do the "make install" and that also went all the way to the end without errors.
I also got a message on the last line
"Yout new glibc installation seems to be ok"
Now the question did I mess up anything by not populating dev ?
Populating /dev is an important part and I doubt you can do without. But you can always try.
I don't think glibc is the problem, but rather something you did or did not do in the previous chapters. I was hoping to get a clue by examining the glibc logfiles. The /dev/null and other /dev related issues could be at the heart of all this.
I am proceding cautiously.
I finished glibc and the readjusting the toolchain and the sanity check went well but now I have a problem at installing binutils 6.13
The expect -c "spawn ls" command is giving me the
"The system has no more ptys." error that is in the book
I hope this is not related to the glibc installation
I put back the commads for populating dev after I finished glibc so I don't think it's caused by that.
I will make a new post for this since this is no longer related to the original post