From: Adrian Bunk <bunk@kernel.org>
To: Jan Dittmer <jdi@l4x.org>
Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 27
Date: Thu, 27 Mar 2008 15:22:21 +0200 [thread overview]
Message-ID: <20080327132221.GA29701@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <621d098f0803270554j287ce58eme4b0e52cb6470154@mail.gmail.com>
On Thu, Mar 27, 2008 at 01:54:23PM +0100, Jan Dittmer wrote:
> On Thu, Mar 27, 2008 at 12:54 PM, Adrian Bunk <bunk@kernel.org> wrote:
> > On Thu, Mar 27, 2008 at 12:32:26PM +0100, Haavard Skinnemoen wrote:
> > > On Thu, 27 Mar 2008 12:47:45 +0200
> > > Adrian Bunk <bunk@kernel.org> wrote:
> > >
> > > > According to Jan's page, there's still a build error with the defconfig:
> > > > http://l4x.org/k/?d=40450#err
> > >
> > > Hmm...that must be a pretty ancient toolchain.
>
> That's the toolchain from back when avr32 was first integrated in the
> kernel. So it may be outdated, but I didn't read any statement on
> the contrary. I tend to keep the toolchains stable as long as
> possible.
>
> > > FWIW, a more recent toolchain is available here:
> > >
> > > http://avr32linux.org/twiki/bin/view/Main/BinutilsPatches
> > > http://avr32linux.org/twiki/bin/view/Main/GccPatches
>
> So how can I get notified if I need a more recent toolchain?
> IMHO every architecture should have a file somewhere (in
> the kernel tree) where the required toolchain versions are
> listed and required patches are linked. That would make it
> such discussions unnecessary.
Even more important, all architectures should get all their
required patches into upstream binutils and gcc.
There might be some time at the beginning of a port until this state is
reached, but for the majority of our architectures plain upstream
binutils 2.18.50.0.5 and gcc 4.3.0 already give a successful kernel
build.
And I'm regularly poking arch maintainers to get their binutils and gcc
patches upstream.
Regarding "required toolchain versions" - I'm not even sure anyone
really knows what the minimum binutils version for x86 is...
> Jan
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-03-27 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 7:33 Stephen Rothwell
2008-03-27 8:49 ` [BUILD_FAILURE] " Kamalesh Babulal
2008-03-27 9:42 ` Haavard Skinnemoen
2008-03-27 10:47 ` Adrian Bunk
2008-03-27 11:32 ` Haavard Skinnemoen
2008-03-27 11:54 ` Adrian Bunk
2008-03-27 12:11 ` Haavard Skinnemoen
2008-03-27 12:54 ` Jan Dittmer
2008-03-27 13:22 ` Adrian Bunk [this message]
2008-03-27 13:31 ` Haavard Skinnemoen
2008-03-27 22:29 ` Stephen Rothwell
2008-03-27 14:45 ` Greg KH
2008-03-28 4:53 ` Stephen Rothwell
2008-03-28 20:27 ` Greg KH
2008-03-29 3:56 ` Stephen Rothwell
2009-03-27 12:19 Stephen Rothwell
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=20080327132221.GA29701@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=haavard.skinnemoen@atmel.com \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®