Dan Nicholson wrote:
On 4/3/06, laurent <[EMAIL PROTECTED]> wrote:
I would try to reinstall chapter 5, and would make the critical test
(like "adjusting the toochain") by hand without bash scripts. Please,
tell me that it will be not necessary!
ARRRRRRRGGGGGGGHHHHHHHH!
1. By hand is good, but the scripts work very well (sometimes better
than human decision making) for this task. As long as you're sure
your script will bomb on a non-zero exit status, you can use grep.
readelf -l a.out | grep ': /tools'
If the interpreter is not under /tools, then grep will return 1 since
it could not match that pattern. If you're scripts are set up to bomb
on errors (look at set -e in the bash docs), then it will stop and you
can debug.
2. Chris' advice to start over from the beginning is wisest.
However, you can probably save yourself some time and have a "clean
enough" toolchain by starting at Adjusting the Toolchain and going
forward. This would save you a gcc bootstrap and glibc build which
are long.
If you're anal and want that squeaky-clean feeling, than start from
the beginning with rm -rf /tools/*.
--
Dan
Ok, I found where the mistake was : I put the command :
ln -vs gcc /tools/bin/cc from gcc pass 1 in chapter 5 after the last
exit in my bash script when i build gcc.
I corrected the problem and now the test with mount goes cool.
I'm surprised that the problem occured only for the binutils package in
the chapter five.
Thank you very much to everyone who tried to help me!
___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
