ct-ng 1.4.2: problem in creating x86_64 toolchain
Yann E. MORIN
yann.morin.1998@anciens.enib.fr
Sat Oct 31 21:06:00 GMT 2009
Zvi, All,
[Please, keep the mailing list copied]
On Saturday 31 October 2009 20:49:14 Zvi Vered wrote:
> On Sat, Oct 31, 2009 at 12:53 PM, Yann E. MORIN
> <yann.morin.1998@anciens.enib.fr> wrote:
> > On Friday 30 October 2009 05:20:10 Zvi Vered wrote:
> >> The toolchain was build OK. When I ran "x86_64-unknown-linux-gnu --v" I got:
> >> Using built-in specs.
> >> Target: x86_64-unknown-linux-gnu
> >> Configured with:
> >> /home/zvivered/GNU/ct-ng-1.4.2/working/src/gcc-4.3.2/configure
> >> --build=i386-build_redhat-linux-gnu --host=i386-build_redhat-linux-gnu
> >> --target=x86_64-unknown-linux-gnu
> > So, your host is an x86, not an x86_64, right?
> You are right.
> >> But when I tried: ldd ld-2.9.so
> > I suppose you're talking about the ld-2.9.so in the sysroot of the
> > toolchain, right?
> Right again.
> > Run "file ld-2.9.so" : what does it tell you?
> I got:
> when I ran "file ld-2.9.so" I got:
> ld-2.9.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV),
> not stripped
OK, then ld.so is OK
> >
> > You should use "x86_64-unknown-linux-gnu-readelf -d" and look at the
> > 'NEEDED' entries.
> >
> I'm not sure what you mean by 'NEEDED' entries. This is what I got
> after readelf:
You ran readelf against ld.so. But being the dynamic loader, it has no
dependency (or we'd have the chicken-n-egg problem!).
You should run readelf against your program (eg. your mapp.out).
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
`------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list