On Monday 16 January 2006 11:24, [EMAIL PROTECTED] wrote:
> ------------------------------
> Thanks Andy for your reply. When i give the ldd /tools/bin/gcc
> command i get:
>
> ldd /mnt/lfs/tools/bin/gcc
> linux-gate.so.1 => (0xffffe000)
> libc.so.6 => /lib/libc.so.6 (0xb7eff000)
> /lib/ld-linux.so.2 (0xb7fee000)
>
> i think you'e right it should be /tools/bin/ld-linux.so2 ?
In 5.7 you have to make that:
SPECFILE=`gcc --print-file specs` &&
sed 's@ /lib/ld-linux.so.2@ /tools/lib/[EMAIL PROTECTED]' \
$SPECFILE > tempspecfile &&
mv -f tempspecfile $SPECFILE &&
unset SPECFILE
It is not a problem of copy and paste than where to start it from.
Starting from the last issues directory? Nowhere in the book is
mentioned where you should be, within which directory. E.g.
starting from the LiveCD is quite a good thing and(!) there you have
the /sources. Forget it. You just have to use it for copying once.
But lets go on.
Then you get the advice to do:
It is recommended that the above command be copy-and-pasted in order to
ensure accuracy. Alternatively, the specs file can be edited by hand.
This is done by replacing every occurrence of ?/lib/ld-linux.so.2? with
?/tools/lib/ld-linux.so.2?
Sorry for having question marks, they are not on the building machine
So what to do? All ../ld-linux.so.2 are logically linked to absolutly
different libs in the different directories called ld-2.3.4.so. Is this
a mistake? Of course it's just the same in /mnt/lfs/tools/lib and it
cant't be something else.
So I did go go with the test
echo 'main(){}' > dummy.c
cc dummy.c
readelf -l a.out | grep ': /tools'
and everthing is as expected. Or as it should be. Or I assume it to be.
But no hint, no answer.
5.4 worked fine, even 5.6 and (!) the make check. Not at the first
time. Oh no! Not at the second, not at the third, .... but finally. So
I get the idea: What about the test? Is the compilation OK and just
the test suite making all the failures? And forget SBU. They are
making funny of you. Never, never use make -k check, you will never
get out what went wrong...
Let's read the Book...
While this may initially seem like a lot of work to isolate the new
system from the host distribution, a full technical explanation is
provided at the beginning of Chapter 5.
Well, well but don't believe it! In 5.2 you can read:
This section explains some of the rationale and technical details
behind the overall build method. It is not essential to immediately
understand everything in this section. Most of this information will be
clearer after performing an actual build.
But how to build to come to an after-actual-build?
> Is every program build in chapter 5 to the host?
It is not absolutly clear. I do have a chance because of a very usefull
configuration of the liveCD, the prompt is with pretty nice colours,
Starting the user lfs with
source ~/.bash_profile
it turns into gray of course. Nothing mentioned nowhere. And root in
the 6. does this too. This is extremlx usefull, not a single word is
mentioned about that in the book. You only don't have any access
to the LiveCD if you are using it what I strongly recommend. If you
didn't copy /sources/* to $LFS/sources/ forget it (Or make [Strg][d]
at another VC :-) But then you are root of LiveCD!!!!)
Another hint? In 5.11 you may read after make:
There is no need to use the bootstrap target now because the compiler
being used to compile this GCC was built from the exact same version of
the GCC sources used earlier.
Don't do it. I did make several times and make check much more
often, no chance. But let's read the next saying:
A few unexpected failures cannot always be avoided.
So if you get failures much later, someone may write to you: You must
have ignored some warnings.... Well, if you compile at a pentium 2 you
can't see it because you did fall asleep, is it a faster machine you
also can't see any warning. But why not make bootstrap every time?
And another thing: Which failures safely can be ignored, which ones not?
Not a single word about that!
>so i best can start
> al over ?
>From the very beginning, because nowhere is mentioned how or where
you can securely start again without mke2fs /dev/hdann .
(nn= numerum nescio)
Clemens
quite frustrated
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
