AW: AW: AW: AW: AW: AW: gcc 4.0.2 build error
Back Michael (extern)
michael.back.ext at siemens.com
Thu Dec 15 00:05:37 PST 2005
>You should have crti.o in /mnt/lfs/tools/lib, from the 32-bit full=20
>glibc, and also in /mnt/lfs/tools/lib64 from the 64-bit full glibc.
>1. find $LFS/tools -name 'crti.o' : do either/both exist ?
Yes, both files exists!
>2. for whichever does exist, run 'file' to confirm you have 32-bit in=20
>lib and 64-bit in lib64.
Both files are the correct one - lib/crti.o is a 32-bit and lib64/crti.o is
>3. are your /tools and /cross-tools symlinks correct ?
The links are correct!
>4. did you install glibc into /cross-tools by accident ?
No, I build both glibc (32/64) to /tools
Is adding -B/tools/lib64 to the build command (xgcc) a solution? If I do
that no error occure!
Maybe I should use the same linux distribution which you and Jim use. Which
one is that? - So I change to this one, maybe it helps!
Which type of machine do you or Jim use to build clfs for test? So I try to
get the same one.
I use a dual opteron on a tyan S2882.
Thanks for the good help!
Von: cross-lfs-bounces at linuxfromscratch.org
[mailto:cross-lfs-bounces at linuxfromscratch.org] Im Auftrag von Ken Moffat
Gesendet: Mittwoch, 14. Dezember 2005 17:59
An: Cross-LFS Discussion List
Betreff: Re: AW: AW: AW: AW: AW: gcc 4.0.2 build error
This message uses a character set that is not supported by the Internet
Service. To view the original message content, open the attached message.
If the text doesn't display correctly, save the attachment to disk, and then
open it using a viewer that can display the original character set.
More information about the cross-lfs