From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] Shell-Weirdness
Date: Thu, 20 Mar 2008 17:12:19 +0000 [thread overview]
Message-ID: <1206033139.2562.48.camel@nigel-x60> (raw)
In-Reply-To: <1206033001.2562.45.camel@nigel-x60>
> The problem is the avr32 patch against GCC.
>
> It took me the past 3 days with Jacmet to track it down.
>
> 900-avr32-atmel.1.3.2.patch <= THAT patch.
>
> I'm still investigating how to fix it.
As the patches after it will more than likely fail ... remove every
patch 900 and above and it works perfectly no problem.
-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://busybox.net/lists/buildroot/attachments/20080320/770ebf23/attachment.pgp
next prev parent reply other threads:[~2008-03-20 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 13:06 [Buildroot] Shell-Weirdness Christof Klaiber
2008-03-20 17:05 ` John Voltz
2008-03-20 17:10 ` Nigel Kukard
2008-03-20 17:12 ` Nigel Kukard [this message]
2008-03-20 17:32 ` John Voltz
2008-03-25 7:12 ` [Buildroot] [BR-AVR32] Shell-Weirdness Hans-Christian Egtvedt
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=1206033139.2562.48.camel@nigel-x60 \
--to=nkukard@lbsd.net \
--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