From: Kai Ruottu <karuottu@mbnet.fi>
To: none none <menwn@yahoo.co.uk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Cross Compile Gcc
Date: Wed, 09 May 2007 17:03:00 -0000 [thread overview]
Message-ID: <4641FFCD.3010803@mbnet.fi> (raw)
In-Reply-To: <876356.86731.qm@web26209.mail.ukl.yahoo.com>
none none wrote:
> I have this very peculiar error when I try to make gcc for cross
compilation with target a powerpc
> on my Ubuntu 7.0.4 box. I keep getting the error:
> make[2]: powerpc-linux-ar: Command not found
>
> and then I export the path with the command:
> export PATH=$PATH:/opt/powerpc/bin
What will be told if you simply write:
sudo powerpc-linux-ar --version
as a command? Is the command found or not after first using the
'export' for redefining PATH?
Usually the $prefix/bin will be puts into the PATH definitions in the
startup-scripts so when opening
a new terminal session the PATH is right and includes ALL the required
search places...
> I configure gcc with the command:
> sudo /home/idipous/Desktop/gcc-4.1.0/configure --target=powerpc-linux
--prefix=/opt/powerpc/
> --disable-shared --disable-threads --enable-languages=c --with-newlib
The 'sudo' probably starts a new shell session as 'root', reads the
startup scripts for root and uses the
PATH got from them... And your earlier 'export' command probably was
totally vain and forgotten...
BTW, what is your goal for the $target ? Someone using Ubuntu 7.0.4/x86
or .../x86_64 could
be expected to be interested to crosscompile to Ubuntu 7.0.4/PPC but
your configure command
clearly tells this not being the case at all! A
Ubuntu/x86-X-Ubuntu/PPC cross-GCC build will
succeed in only one build step, producing C/C++/Fortran/Java etc.
compilers and all the shared libs
with threads support etc.
next prev parent reply other threads:[~2007-05-09 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 11:30 none none
2007-05-09 16:00 ` David Daney
2007-05-09 17:03 ` Kai Ruottu [this message]
2007-05-12 14:11 none none
2007-05-12 14:25 ` Tim Prince
2007-05-12 15:59 none none
2007-05-13 17:38 ` Kai Ruottu
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=4641FFCD.3010803@mbnet.fi \
--to=karuottu@mbnet.fi \
--cc=gcc-help@gcc.gnu.org \
--cc=menwn@yahoo.co.uk \
/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).