From: rodolfo <rodolfo@lesc.ufc.br>
To: John Linn <John.Linn@xilinx.com>
Cc: linuxppc-embedded@ozlabs.org, Mirek23 <miroslaw.dach@psi.ch>
Subject: RE: Cross toolchain for ppc405 (virtex-4)
Date: Wed, 28 May 2008 15:05:04 -0300 [thread overview]
Message-ID: <a949fe6be8a76bc2ecfa56313f8e7047@lesc.ufc.br> (raw)
In-Reply-To: <20080528171751.D545CBD8071@mail116-sin.bigfish.com>
Hi Jonh,
If I use ml403 (with PPC 405) Did i change the predefined compiler flags
for ppc_4xx? The default value is -mcpu=403.
On Wed, 28 May 2008 11:16:41 -0600, "John Linn" <John.Linn@xilinx.com>
wrote:
> Hi Miroslaw,
>
> I'm not sure on what version of gcc and glibc it's using, but I have been
> using ELDK 4.1 from denx.com. There are newer versions.
>
> Thanks,
> John
>
>
>
> -----Original Message-----
> From: linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org on behalf
> of Mirek23
> Sent: Wed 5/28/2008 9:54 AM
> To: linuxppc-embedded@ozlabs.org
> Subject: Cross toolchain for ppc405 (virtex-4)
>
>
> Hi All,
>
> I am using for some time the crosstool tool-chain (crosstool-0.43) for
the
> ppc405 of my virtex-4.
> It seems to be that the crosstool was not updated for awhile but the
glibc
> and gcc compiler has changed a bit meanwhile.
>
> The latest working configuration to build the toolchain for ppc405 is
> gcc-4.1.0-glibc-2.3.6.dat
> Does any body has tried to adapt the crosstools to use for example glibc
> 2.7
> ?
>
> Another alternative would be to use another tool than crosstool. Could
> somebody recommend something which can refer to newer version of gcc and
> glibc .
>
> Best Regards
>
> Miroslaw Dach
>
>
next prev parent reply other threads:[~2008-05-28 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 15:54 Cross toolchain for ppc405 (virtex-4) Mirek23
2008-05-28 17:16 ` John Linn
2008-05-28 18:05 ` rodolfo [this message]
2008-05-28 19:32 ` John Linn
2008-05-28 19:59 ` rodolfo
2008-05-29 6:40 ` David H. Lynch Jr.
2008-05-29 11:29 ` Detlev Zundel
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=a949fe6be8a76bc2ecfa56313f8e7047@lesc.ufc.br \
--to=rodolfo@lesc.ufc.br \
--cc=John.Linn@xilinx.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=miroslaw.dach@psi.ch \
/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 NNTP newsgroup(s).