From: Guenter Roeck <linux@roeck-us.net>
To: Linux MIPS Mailing List <linux-mips@linux-mips.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Alex Smith <alex.smith@imgtec.com>
Subject: Mips build errors in next-20151020
Date: Tue, 20 Oct 2015 11:48:32 -0700 [thread overview]
Message-ID: <56268C80.5020903@roeck-us.net> (raw)
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
next reply other threads:[~2015-10-20 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 18:48 Guenter Roeck [this message]
2015-10-21 8:04 ` Mips build errors in next-20151020 Markos Chandras
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=56268C80.5020903@roeck-us.net \
--to=linux@roeck-us.net \
--cc=alex.smith@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@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 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.