From: Bob Koninckx <bob.koninckx@mech.kuleuven.ac.be>
To: David Korn <dkorn@pixelpower.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Cross compiler Alpha->powerpc problems
Date: Mon, 26 Mar 2001 05:17:00 -0000 [thread overview]
Message-ID: <3ABF4F4E.FA0888AF@mech.kuleuven.ac.be> (raw)
In-Reply-To: <718D38CAB6E0D011B2C90060970C28A56427C4@exchangeserver.pixelpower.com>
David Korn wrote:
> >-----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.
I don't think that is the problem. Actually, the prefix and exec-prefix
directories fr both binutils and gcc were
/usr/local/crossgcc/powerpc-eabi. So there is an extra powerpc-eabi directory
(the one you
are referring too) underneath. Moreover, The procedure works fine for the
i386-elf or m68k-coff targets
that were build in exactly the same way.
(
There are thus
/usr/local/crossgcc/powerpc-eabi/bin and
/usr/local/crossgcc/powerpc-eabi/powerpc-eabi/bin directories
)
>
> 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.
As stated before that is what it finds. The fact that the problem only occurs
for the powerpc-eabi
target makes me believe that it has something to do with that target, rather
than with the build procedure
>
>
> 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?
Yep, linux on an alpha workstation. The identical procedure on an i386 host
runs without any problems.
>
> Have you joined the eCos mailing list?
Well, I searched the archives and came accross a problem for building the
tools on an alpha for an arm target.
The solution to that problem was upgrading the host compiler to at least
2.95.2. I didn't find anything concerning
the powerpc. However, I found the hint to ask gcc related questions on this
list several times. That's why I asked
it here.
> Did you apply the path from
> http://sources.redhat.com/ecos/tools/patches/ecos-gcc-2952.pat
> to the gcc source code?
Yes, I did.
>
>
> DaveK
Thanks for your help anyway. Maybe other suggestions ??
Regards,
Bob
>
> --
> 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 prev parent reply other threads:[~2001-03-26 5:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 4:38 David Korn
2001-03-26 5:17 ` Bob Koninckx [this message]
-- 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=3ABF4F4E.FA0888AF@mech.kuleuven.ac.be \
--to=bob.koninckx@mech.kuleuven.ac.be \
--cc=dkorn@pixelpower.com \
--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).