From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] meaning of BR2_arm_dunno
Date: Sat, 31 Jan 2009 11:26:12 +0100 [thread overview]
Message-ID: <20090131102612.GA6794@mx.loc> (raw)
In-Reply-To: <87wscdm3rf.fsf@macbook.be.48ers.dk>
On Fri, Jan 30, 2009 at 12:28:52PM +0100, Peter Korsgaard wrote:
>>>>>> "Sven" == Sven Neumann <s.neumann@phase-zero.de> writes:
>
> Sven> Hi,
> Sven> On Fri, 2009-01-30 at 11:23 +0100, Peter Korsgaard wrote:
>
> Sven> BR2_GCC_TARGET_ABI="aapcs" seems to be accepted. I will try to compile
> Sven> my tree with this option now and also check if I can build a recent
> Sven> kernel using the compiler that results from this build...
> >>
> >> Ok, thanks, otherwise I'll take the gcc patch so aapcs-linux works.
>
> Sven> I've successfully built the system, booted it and run some tests. I also
> Sven> verified that I can build 2.6.29-rc3 using the kernel created by this
> Sven> build. Attached is a patch with the change.
>
>Thanks, but I think the correct thing is to use aapcs-linux (E.G. so
>it also works with older toolchains), and patch gcc 4.3.2 to accept
>that (like Bernhard already did).
I think this is/will be fixed in gcc-4.4.0 and 4.3.3
>
>I've checked in that patch already and will fix up the stuff in
>Config.in.arch now.
As already mentioned several times somewhere else, you should synch
(these parts of) your tree against improvements that went into my
tree. This poor guy wouldn't have been bitten by this issue, fwiw.
next prev parent reply other threads:[~2009-01-31 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 15:30 [Buildroot] meaning of BR2_arm_dunno Sven Neumann
2009-01-29 15:46 ` Peter Korsgaard
2009-01-29 16:11 ` Sven Neumann
2009-01-29 16:16 ` Peter Korsgaard
2009-01-30 10:01 ` Sven Neumann
2009-01-30 10:14 ` Sven Neumann
2009-01-30 10:23 ` Peter Korsgaard
2009-01-30 11:25 ` Sven Neumann
2009-01-30 11:28 ` Peter Korsgaard
2009-01-31 10:26 ` Bernhard Reutner-Fischer [this message]
2009-01-31 22:28 ` Peter Korsgaard
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=20090131102612.GA6794@mx.loc \
--to=rep.dot.nop@gmail.com \
--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