mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.4
Date: Mon, 11 Jan 2016 03:14:37 -0800	[thread overview]
Message-ID: <20160111111437.GA19316@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdUNY_wyks7ifndgKUgEPjtRX4Jky+0fD9ACtcF1KHhjMQ@mail.gmail.com>

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/cc0jJBdq.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 43
>   + /tmp/ccAZ4Auh.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 43
>   + /tmp/ccB0ZRvh.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 403, 41
>   + /tmp/ccMX3tVu.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 43
>   + /tmp/ccRRACJX.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 43
>   + /tmp/ccV0AVwo.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 44
>   + /tmp/ccYG07Rw.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 49, 378
>   + /tmp/ccZgopoJ.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 49, 366
>   + /tmp/ccdDASPC.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 43
>   + /tmp/cclXFWlr.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}:  => 43
>   + /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.

Thanks,
Guenter

  reply	other threads:[~2016-01-11 11:14 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 [this message]
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
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=20160111111437.GA19316@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome