From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: Build regressions/improvements in v3.6-rc6
Date: Tue, 18 Sep 2012 20:15:29 +0200 [thread overview]
Message-ID: <CAMuHMdUDQTUvFNavKy6VX1LNqy4jJ_OyMusu86eVd7QspzbUCw@mail.gmail.com> (raw)
In-Reply-To: <1347991700-22730-1-git-send-email-geert@linux-m68k.org>
On Tue, Sep 18, 2012 at 8:08 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> JFYI, when comparing v3.6-rc6 to v3.6-rc5[3], the summaries are:
> - build errors: +14/-16
14 regressions:
+ arch/powerpc/mm/tlb_nohash_low.S: Error: bad expression: => 212,
234, 232, 230
+ arch/powerpc/mm/tlb_nohash_low.S: Error: junk at end of line,
first unrecognized character is `r': => 212, 234, 232, 230
+ arch/powerpc/mm/tlb_nohash_low.S: Error: missing ')': => 212, 234, 232, 230
44x/currituck_defconfig
+ error: ci13xxx_imx.c: undefined reference to `devm_clk_get': =>
.devinit.text+0x4b154)
+ error: exynos-rng.c: undefined reference to `devm_clk_get': =>
.devinit.text+0x2da54)
+ error: flexcan.c: undefined reference to `devm_clk_get': =>
.devinit.text+0x43148), .devinit.text+0x430c8)
powerpc-randconfig
+ error: fore200e.c: relocation truncated to fit: R_PPC64_REL24
against symbol `.ktime_get_real' defined in .text section in
kernel/built-in.o: => (.text+0x1ff8928)
+ error: fore200e.c: relocation truncated to fit: R_PPC64_REL24
against symbol `.msecs_to_jiffies' defined in .text section in
kernel/built-in.o: => (.text+0x1ff9068)
+ error: fore200e.c: relocation truncated to fit: R_PPC64_REL24
against symbol `.panic' defined in .text.unlikely section in
kernel/built-in.o: => (.text+0x1ff9be4)
+ error: fore200e.c: relocation truncated to fit: R_PPC64_REL24
against symbol `_restgpr0_14' defined in .text.save.restore section in
arch/powerpc/lib/built-in.o: => (.text+0x1ff876c)
+ error: fore200e.c: relocation truncated to fit: R_PPC64_REL24
against symbol `_savegpr0_20' defined in .text.save.restore section in
arch/powerpc/lib/built-in.o: => (.text+0x1ff8774)
+ error: fore200e.c: relocation truncated to fit: R_PPC64_REL24
against symbol `_savegpr0_23' defined in .text.save.restore section in
arch/powerpc/lib/built-in.o: => (.text+0x1ff9358)
+ error: fore200e.c: relocation truncated to fit: R_PPC64_REL24
against symbol `_savegpr0_29' defined in .text.save.restore section in
arch/powerpc/lib/built-in.o: => (.text+0x1ff8ebc)
powerpc-allyesconfig
+ kernel/sys.c: error: 'mmap_min_addr' undeclared (first use in this
function): 1868:34 => 1868:37, 1868:34
sh-allyesconfig, sh-allmodconfig, sh-randconfig
> [1] http://kisskb.ellerman.id.au/kisskb/head/5424/ (117 out of 116 configs)
Doh, forgot to update my scripts for the increase in configs...
> [3] http://kisskb.ellerman.id.au/kisskb/head/5400/ (all 116 configs)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
parent reply other threads:[~2012-09-18 18:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1347991700-22730-1-git-send-email-geert@linux-m68k.org>]
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=CAMuHMdUDQTUvFNavKy6VX1LNqy4jJ_OyMusu86eVd7QspzbUCw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).