From: Markos Chandras <Markos.Chandras@imgtec.com>
To: <linux-mips@linux-mips.org>
Subject: Re: Mips build errors in next-20151020
Date: Wed, 21 Oct 2015 09:04:13 +0100 [thread overview]
Message-ID: <562746FD.9030204@imgtec.com> (raw)
In-Reply-To: <56268C80.5020903@roeck-us.net>
On 10/20/2015 07:48 PM, Guenter Roeck wrote:
> Hi all,
>
> all mips images fail to build for me in next-20151020 as follows.
>
> Building mips:defconfig ... failed
> --------------
> Error log:
> /tmp/cc9iCAqK.s: Assembler messages:
> /tmp/cc9iCAqK.s:50: Error: can't resolve `_start' {*UND* section} -
> `L0\x01' {.text section}
> /tmp/cc9iCAqK.s:374: Error: can't resolve `_start' {*UND* section} -
> `L0\x01' {.text section}
> make[2]: *** [arch/mips/vdso/gettimeofday.o] Error 1
> make[1]: *** [arch/mips/vdso] Error 2
>
> Toolchain is "mips-poky-linux-gcc (GCC) 4.7.2".
>
> Do I need a new toolchain ?
>
> Thanks,
> Guenter
>
I am working on that with Ralf. seems like we are going to need
binutils-2.25 for the VDSO code and disable it for older versions. I
will post new patches today.
--
markos
WARNING: multiple messages have this Message-ID (diff)
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: linux-mips@linux-mips.org
Subject: Re: Mips build errors in next-20151020
Date: Wed, 21 Oct 2015 09:04:13 +0100 [thread overview]
Message-ID: <562746FD.9030204@imgtec.com> (raw)
Message-ID: <20151021080413.-6okKUJ7nSEA-XrCQWR7usnJj49Z-roV-v7GhJ6ffyU@z> (raw)
In-Reply-To: <56268C80.5020903@roeck-us.net>
On 10/20/2015 07:48 PM, Guenter Roeck wrote:
> Hi all,
>
> all mips images fail to build for me in next-20151020 as follows.
>
> Building mips:defconfig ... failed
> --------------
> Error log:
> /tmp/cc9iCAqK.s: Assembler messages:
> /tmp/cc9iCAqK.s:50: Error: can't resolve `_start' {*UND* section} -
> `L0\x01' {.text section}
> /tmp/cc9iCAqK.s:374: Error: can't resolve `_start' {*UND* section} -
> `L0\x01' {.text section}
> make[2]: *** [arch/mips/vdso/gettimeofday.o] Error 1
> make[1]: *** [arch/mips/vdso] Error 2
>
> Toolchain is "mips-poky-linux-gcc (GCC) 4.7.2".
>
> Do I need a new toolchain ?
>
> Thanks,
> Guenter
>
I am working on that with Ralf. seems like we are going to need
binutils-2.25 for the VDSO code and disable it for older versions. I
will post new patches today.
--
markos
next prev parent reply other threads:[~2015-10-21 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 18:48 Mips build errors in next-20151020 Guenter Roeck
2015-10-21 8:04 ` Markos Chandras [this message]
2015-10-21 8:04 ` Markos Chandras
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=562746FD.9030204@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=linux-mips@linux-mips.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 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.