From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: "Iztok Fister" <iztok.fister@elti.si>
Cc: crossgcc@sourceware.org
Subject: Re: *** SPAM ***The question
Date: Wed, 16 Dec 2009 22:15:00 -0000 [thread overview]
Message-ID: <200912162315.37808.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <FD75020B440E1547A4644911ED1B5A09A1C2C9@buda.elti.local>
Hello Iztok!
Please, use the crossgcc mailing list for such questions.
On Tuesday 08 December 2009 13:07:59 Iztok Fister wrote:
> I thank you for using your cross compiler toolchain crosstools-NG that
> I have been generated for processor GENE-5315 based on AMD Geode
> processors.
> While compiling the program HelloWorld.c the following messages were
> arisen:
Note that semingly-native toolchains may have issues, look at:
docs/known-issues.txt
But yours seems different...
> GNU C (crosstool-NG-1.5.2) version 4.3.2 (i686-unknown-linux-gnu)
> compiled by GNU C version 4.4.1 20090725 (Red Hat 4.4.1-2), GMP
> version 4.2.2, MPFR version 2.3.2.
> warning: GMP header version 4.2.2 differs from library version 4.2.4.
> warning: MPFR header version 2.3.2 differs from library version 2.4.1.
Woops... Something is wrong here. It looks as though the build did not
complete properly: finding the correct gmp/mpfr libraries should be
gracefully handled by the wrappers that are isntalled at the end of the
build. Could you run:
ls -A1 /root/x-tools/i686-unknown-linux-gnu/i686-unknown-linux-gnu/bin
'--> this is a 'one', not an 'ell'.
You should have something along the lines of:
.i686-unknown-linux-gnu-as
.i686-unknown-linux-gnu-g++
.i686-unknown-linux-gnu-gcc
.i686-unknown-linux-gnu-gcc-4.4.2
.i686-unknown-linux-gnu-gdb
.i686-unknown-linux-gnu-ld
.i686-unknown-linux-gnu-readelf
i686-unknown-linux-gnu-as
i686-unknown-linux-gnu-g++
i686-unknown-linux-gnu-gcc
i686-unknown-linux-gnu-gcc-4.4.2
i686-unknown-linux-gnu-gdb
i686-unknown-linux-gnu-ld
i686-unknown-linux-gnu-readelf
(I stripped the list for brevity)
If your list is not similar to the above, that is for every
i686-unknown-linux-gnu-XXX there is a .i686-unknown-linux-gnu-XXX
then the build was screwed.
Oh, by the way. Looks like you installed as root. Don't. It might break
things doing so.
> as -V -Qy -osrc/Hello.o /tmp/cc8yzhix.s
> GNU assembler version 2.19.51.0.14 (i586-redhat-linux) using BFD version
> version 2.19.51.0.14-1.fc11 20090722
It is taking your _native_ 'as'. Weird. Definitely, something went wrong.
> ld: this linker was not configured to use sysroots
Yep. Native tools are not build for using sysroot. Looks like it also
picked your native 'ld'.
Try rebuilding the toolchain from scratch, as non-root.
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
parent reply other threads:[~2009-12-16 22:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <FD75020B440E1547A4644911ED1B5A09A1C2C9@buda.elti.local>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200912162315.37808.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=iztok.fister@elti.si \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).