[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56973924.4080301@roeck-us.net>
Date: Wed, 13 Jan 2016 21:59:00 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Michael Ellerman <mpe@...erman.id.au>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: Build regressions/improvements in v4.4
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@...ck-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@...ux-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?
>
Hopefully not. Mainline should build for you now, and we'll have
to make sure that commit d5ece1cb074b is applied to 4.4.
Guenter
Powered by blists - more mailing lists