From: David Korn <dkorn@pixelpower.com>
To: "'bob.koninckx@mech.kuleuven.ac.be'"
<bob.koninckx@mech.kuleuven.ac.be>,
gcc-help@gcc.gnu.org
Subject: RE: Cross compiler Alpha->powerpc problems
Date: Mon, 26 Mar 2001 04:38:00 -0000 [thread overview]
Message-ID: <718D38CAB6E0D011B2C90060970C28A56427C4@exchangeserver.pixelpower.com> (raw)
>-----Original Message-----
>From: Bob Koninckx [ mailto:bob.koninckx@mech.kuleuven.ac.be ]
>Sent: 25 March 2001 11:30
>## PATH=/usr/local/crossgcc/powerpc-eabi/bin:$PATH; export PATH
Don't do this.
In the $prefix/$target/bin directory, you have cross binutils, with
no '$target-' prefix. Putting this directory first in your path means that
whenever gcc tries to invoke 'as', it will find the ppc cross assembler and
run that. That's not what you want; you want to find the native assembler,
since you're building a compiler that's meant to run on your alpha, not
your ppc.
What you really wanted was
PATH=/usr/local/crossgcc/bin:$PATH; export PATH
so that the cross compile process can find the cross binutils under the
name 'powerpc-eabi-as' etc.
Clear everything out and try again with this version of the path setting.
I can't promise that this is the solution to your problem, but it's
still necessary; I've always had mysterious build errors when I've made
that mistake myself.
BTW, http://sources.redhat.com/ecos/getstart.html only mentions the
tools as running under Linux and Windows, so you may find that they
don't build correctly under Alpha? Or are you running Linux on Alpha?
Have you joined the eCos mailing list? Did you apply the path from
http://sources.redhat.com/ecos/tools/patches/ecos-gcc-2952.pat
to the gcc source code?
DaveK
--
All your base are belong to us!
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
next reply other threads:[~2001-03-26 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 4:38 David Korn [this message]
2001-03-26 5:17 ` Bob Koninckx
-- strict thread matches above, loose matches on Subject: below --
2001-03-25 3:31 Bob Koninckx
2001-03-26 19:52 ` Alexandre Oliva
2001-03-26 22:55 ` Bob Koninckx
2001-03-27 13:06 ` Alexandre Oliva
2001-03-28 0:50 ` Bob Koninckx
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=718D38CAB6E0D011B2C90060970C28A56427C4@exchangeserver.pixelpower.com \
--to=dkorn@pixelpower.com \
--cc=bob.koninckx@mech.kuleuven.ac.be \
--cc=gcc-help@gcc.gnu.org \
/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).