From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 libiberty build failure
Date: Tue, 18 Sep 2007 13:26:36 +0200 [thread overview]
Message-ID: <20070918112636.GA2231@aon.at> (raw)
In-Reply-To: <46EF36B4.2000703@tait.co.nz>
On Tue, Sep 18, 2007 at 02:23:48PM +1200, Robin Gilks wrote:
> At least I think thats the problem...
>
> gcc builds OK and at the next step on a default config build for a atngw100
> it fails.
Does this work with the current stable, buildroot gcc, i.e. our 4.2.1 with
buildroot patches?
It seems that you are using something like:
toolchain_build_avr32/gcc-4.1.2-avr32-2.0
next prev parent reply other threads:[~2007-09-18 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 2:23 [Buildroot] AVR32 libiberty build failure Robin Gilks
2007-09-18 11:26 ` Bernhard Fischer [this message]
2007-09-18 14:26 ` Ulf Samuelsson
2007-09-19 4:23 ` Robin Gilks
2007-09-19 5:00 ` Ulf Samuelsson
2007-09-19 23:17 ` Robin Gilks
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=20070918112636.GA2231@aon.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.