From: Guenter Roeck <linux@roeck-us.net>
To: Michael Ellerman <mpe@ellerman.id.au>,
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: Mon, 18 Jan 2016 16:02:24 -0800 [thread overview]
Message-ID: <569D7D10.1010609@roeck-us.net> (raw)
In-Reply-To: <1453160050.24878.2.camel@ellerman.id.au>
On 01/18/2016 03:34 PM, Michael Ellerman wrote:
> 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
>
Odd, that works just fine for me when building v4.4. It correctly detects
that it can not build vdso and skips it as expected.
Puzzled ...
Guenter
prev parent reply other threads:[~2016-01-19 0:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 8:28 Build regressions/improvements in v4.4 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
2016-01-19 0:02 ` Guenter Roeck [this message]
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=569D7D10.1010609@roeck-us.net \
--to=linux@roeck-us.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.