From: James Hogan <james.hogan@imgtec.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Build regressions/improvements in v4.5-rc7
Date: Tue, 08 Mar 2016 14:35:32 +0000 [thread overview]
Message-ID: <20160308143532.GN31414@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <CAMuHMdWe9bTjp-qmTJc9=n9-iP-qH8-O0jafiRD3-y_EtT=WvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3047 bytes --]
Hi,
On Mon, Mar 07, 2016 at 10:01:09AM +0100, Geert Uytterhoeven wrote:
> On Mon, Mar 7, 2016 at 9:55 AM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > JFYI, when comparing v4.5-rc7[1] to v4.5-rc6[3], the summaries are:
> > - build errors: +8/-7
> + error: debugfs.c: undefined reference to `clk_round_rate': =>
> .text+0x11b9e0)
>
> arm-randconfig
>
> While looking for more context, I noticed another regression that fell through
> the cracks of my script:
>
> arch/arm/kernel/head.o: In function `stext':
> (.head.text+0x40): undefined reference to `CONFIG_PHYS_OFFSET'
> drivers/built-in.o: In function `v4l2_clk_set_rate':
> debugfs.c:(.text+0x11b9e0): undefined reference to `clk_round_rate'
>
> + error: misc.c: undefined reference to `ftrace_likely_update': =>
> .text+0x714), .text+0x94c), .text+0x3b8), .text+0xc10)
>
> sh-randconfig
>
> arch/sh/boot/compressed/misc.o: In function `lzo1x_decompress_safe':
> misc.c:(.text+0x3b8): undefined reference to `ftrace_likely_update'
> misc.c:(.text+0x714): undefined reference to `ftrace_likely_update'
> misc.c:(.text+0x94c): undefined reference to `ftrace_likely_update'
> arch/sh/boot/compressed/misc.o: In function `unlzo.constprop.2':
> misc.c:(.text+0xc10): undefined reference to `ftrace_likely_update'
>
> + /tmp/cc52LvuK.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}: => 41, 403
> + /tmp/ccHfoDA4.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}: => 43
> + /tmp/cch1r0UQ.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}: => 49, 378
> + /tmp/ccoHdFI8.s: Error: can't resolve `_start' {*UND* section} -
> `L0^A' {.text section}: => 43
>
> mips-allnoconfig
> bigsur_defconfig
> malta_defconfig
> cavium_octeon_defconfig
>
> Not really new, but it would be great if the MIPS people could get this
> fixed for the final release.
This would appear to be related to the ld version check for VDSO
failing.
awk: /home/kisskb/slave/src/scripts/ld-version.sh: line 4: regular expression compile failed (missing '(')
.*)
/bin/sh: 1: [: -lt: unexpected operator
I.e. this line:
gsub(".*)", "");
appears to be trying to turn e.g. "GNU ld (Gentoo 2.25.1 p1.1) 2.25.1"
into " 2.25.1", so perhaps the bracket should be escaped. What version
of awk is it using? (GNU Awk 4.0.2 works for me).
Can somebody experiencing this please try:
${CROSS_COMPILE}ld --version | ./scripts/ld-version.sh
with the following patch, to see if it helps.
Thanks
James
diff --git a/scripts/ld-version.sh b/scripts/ld-version.sh
index 198580d245e0..1659b409ef10 100755
--- a/scripts/ld-version.sh
+++ b/scripts/ld-version.sh
@@ -1,7 +1,7 @@
#!/usr/bin/awk -f
# extract linker version number from stdin and turn into single number
{
- gsub(".*)", "");
+ gsub(".*\\)", "");
split($1,a, ".");
print a[1]*10000000 + a[2]*100000 + a[3]*10000 + a[4]*100 + a[5];
exit
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-08 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457340934-23042-1-git-send-email-geert@linux-m68k.org>
2016-03-07 9:01 ` Build regressions/improvements in v4.5-rc7 Geert Uytterhoeven
2016-03-08 14:35 ` James Hogan [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=20160308143532.GN31414@jhogan-linux.le.imgtec.org \
--to=james.hogan@imgtec.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).