[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <621d098f0803270554j287ce58eme4b0e52cb6470154@mail.gmail.com>
Date: Thu, 27 Mar 2008 13:54:23 +0100
From: "Jan Dittmer" <jdi@....org>
To: "Adrian Bunk" <bunk@...nel.org>
Cc: "Haavard Skinnemoen" <haavard.skinnemoen@...el.com>,
"Stephen Rothwell" <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for March 27
On Thu, Mar 27, 2008 at 12:54 PM, Adrian Bunk <bunk@...nel.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@...nel.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.
Jan
--
Jan Dittmer
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists