From: Michael Ellerman <mpe@ellerman.id.au>
To: Guenter Roeck <linux@roeck-us.net>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Build regressions/improvements in v4.4
Date: Tue, 19 Jan 2016 10:34:10 +1100 [thread overview]
Message-ID: <1453160050.24878.2.camel@ellerman.id.au> (raw)
In-Reply-To: <569D13BB.5090707@roeck-us.net>
On Mon, 2016-01-18 at 08:32 -0800, Guenter Roeck wrote:
> On 01/13/2016 09:44 PM, Michael Ellerman wrote:
> > On Mon, 2016-01-11 at 12:38 +0100, Geert Uytterhoeven wrote:
> > > Hi Günter,
> > > On Mon, Jan 11, 2016 at 12:14 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> > > > On Mon, Jan 11, 2016 at 09:29:52AM +0100, Geert Uytterhoeven wrote:
> > > > > On Mon, Jan 11, 2016 at 9:28 AM, Geert Uytterhoeven
> > > > > <geert@linux-m68k.org> wrote:
> > > > > > JFYI, when comparing v4.4[1] to v4.4-rc8[3], the summaries are:
> > > > > > - build errors: +13/-13
> > > > > > [1] http://kisskb.ellerman.id.au/kisskb/head/9774/ (all 259 configs)
> > > > >
> > > > > + /tmp/ccnzCwY6.s: Error: can't resolve `_start' {*UND* section} -
> > > > > `L0^A' {.text section}: => 43
> > > > > + /tmp/ccyAN6Ix.s: Error: can't resolve `_start' {*UND* section} -
> > > > > `L0^A' {.text section}: => 43
> > > > >
> > > > > Various MIPS, the saga continues...
> > > >
> > > > Hi Geert,
> > > >
> > > > do you know which version of binutils is used by kisskb ?
> > > > If it is 2.23.90 or similar (ie below 2.24 and third level version
> > > > has more than one digit), there is a patch pending to fix it.
> > >
> > > No, I don't know.
> >
> > It dumps the GCC version, but not binutils. I should add that one day.
> >
> > The mips toolchain is pretty old, so it's using binutils 2.22. Are you saying I
> > need to update it?
> >
> Michael,
>
> is your toolchain available somewhere as binary ? I'd like to add a single
> mips build test using it if possible.
Hi Guenter,
I'm still using this old one from kernel.org:
https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.3/x86_64-gcc-4.6.3-nolibc_mips-linux.tar.bz2
cheers
next prev parent reply other threads:[~2016-01-18 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 8:28 Geert Uytterhoeven
2016-01-11 8:29 ` Geert Uytterhoeven
2016-01-11 11:14 ` Guenter Roeck
2016-01-11 11:38 ` Geert Uytterhoeven
2016-01-14 5:44 ` Michael Ellerman
2016-01-14 5:59 ` Guenter Roeck
2016-01-18 16:32 ` Guenter Roeck
2016-01-18 23:34 ` Michael Ellerman [this message]
2016-01-19 0:02 ` Guenter Roeck
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=1453160050.24878.2.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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
Powered by JetHome