From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001615]: Can not build?
Date: Fri, 25 Apr 2008 10:25:57 +0200 [thread overview]
Message-ID: <08f001c8a6ad$ff56a2c0$ad289e86@LPSC0173W> (raw)
In-Reply-To: d9108c1a28f74978335988de086eeb18@busybox.net
I've had this eabi problem too when trying to use the Xilinx compilers and
toolchain from .../xilinx/edk/gnu/powerpc-eabi/lin/bin/
I exchanged some messages with tech support that kind of hinted that I
wouldn't be able to compile a kernel with it (I have no idea why). So I did
it with the buildroot toolchain instead and haven't looked back.
I also noticed those ARM keywords at the time, I think they go away if you
"make ARCH=ppc".
--
Guillaume Dargaud
http://www.gdargaud.net/
next prev parent reply other threads:[~2008-04-25 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 20:55 [Buildroot] [buildroot 0001615]: Can not build? bugs at busybox.net
2008-04-25 8:25 ` Guillaume Dargaud [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-28 7:57 bugs at busybox.net
2007-11-28 7:04 bugs at busybox.net
2007-11-28 7:00 bugs at busybox.net
2007-11-28 6:47 bugs at busybox.net
2007-11-28 6:28 bugs at busybox.net
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='08f001c8a6ad$ff56a2c0$ad289e86@LPSC0173W' \
--to=dargaud@lpsc.in2p3.fr \
--cc=buildroot@busybox.net \
/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