All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH 6/6] angstrom: use GCC 4.3.3 for Geode devices
Date: Wed, 13 May 2009 19:10:56 +0200	[thread overview]
Message-ID: <gueuv0$mjh$1@ger.gmane.org> (raw)
In-Reply-To: <20090513151848.GI7973@smtp.west.cox.net>

On 13-05-09 17:18, Tom Rini wrote:
> On Wed, May 13, 2009 at 04:56:58PM +0200, Koen Kooi wrote:
>> On 13-05-09 16:46, Marcin Juszkiewicz wrote:
>>> From: Marcin Juszkiewicz<hrw@openembedded.org>
>>>
>>>
>>> Signed-off-by: Marcin Juszkiewicz<hrw@openembedded.org>
>>> ---
>>>    conf/distro/angstrom-2008.1.conf |    1 +
>>>    1 files changed, 1 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/conf/distro/angstrom-2008.1.conf b/conf/distro/angstrom-2008.1.conf
>>> index a466834..b5dbc48 100644
>>> --- a/conf/distro/angstrom-2008.1.conf
>>> +++ b/conf/distro/angstrom-2008.1.conf
>>> @@ -101,6 +101,7 @@ ANGSTROM_GCC_VERSION_bfin			= "4.1.2"
>>>
>>>    ANGSTROM_GCC_VERSION_486sx      = "4.3.3"
>>>    ANGSTROM_GCC_VERSION_armv7a     = "4.3.3"
>>> +ANGSTROM_GCC_VERSION_geode      = "4.3.3"
>>>
>>>    # Uncomment this if want need to build an armv7a kernel with CSL toolchain (<2.6.27 don't boot with mainline gcc)
>>>    #KERNEL_CCSUFFIX_armv7a= "-4.2.1+csl-arm-2007q3-53"
>>
>> NAK, this would interfere with an outstanding patch that Graeme and I
>> are testing:
>>
>> http://dominion.thruhere.net/koen/OE/angstrom-dev-toolchain.diff
>
> wrt that patch, is there a reason you aren't bumping ppc as well?  As an
> old PPC guy, that's always had me perplexed..

When adding PPC support I had loads of troubles compiling gcc and glibc 
due to sqrt and type size problems.
My efika is too busy serving stuff to serve as a testbed and my 
dht-walnut lacks a psu currently, so I'm a bit apprehensive about 
bumping toolchains without runtime testing them.
If console-image actually builds with gcc 4.3.3 + binutils 2.18, that 
would be a *huge* step forward.

regards,

Koen





  parent reply	other threads:[~2009-05-13 17:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 14:46 Some updates for GeodeLX based devices Marcin Juszkiewicz
2009-05-13 14:46 ` [PATCH 1/6] Remove alix machine, update geodelx one to use Alix settings Marcin Juszkiewicz
2009-05-13 14:46 ` [PATCH 2/6] kaeilos/sane-feed: remove alix, mark geodelx as i586 Marcin Juszkiewicz
2009-05-13 14:46 ` [PATCH 3/6] kaeilos.inc/sane-feed.inc: use spaces instead of tabs Marcin Juszkiewicz
2009-05-13 14:46 ` [PATCH 4/6] kaeilos: use include/sane-feed.inc Marcin Juszkiewicz
2009-05-13 14:46 ` [PATCH 5/6] linux: drop alix, move geodelx to 2.6.29 Marcin Juszkiewicz
2009-05-13 14:46 ` [PATCH 6/6] angstrom: use GCC 4.3.3 for Geode devices Marcin Juszkiewicz
2009-05-13 14:56   ` Koen Kooi
2009-05-13 15:18     ` Tom Rini
2009-05-13 15:22       ` Philip Balister
2009-05-13 15:48         ` Tom Rini
2009-05-13 19:36           ` Tom Rini
2009-05-13 20:43             ` Koen Kooi
2009-05-13 17:10       ` Koen Kooi [this message]
2009-05-13 18:01         ` Leon Woestenberg
2009-05-13 18:11           ` Koen Kooi
2009-05-13 17:37     ` Marcin Juszkiewicz

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='gueuv0$mjh$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /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.