From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Build regressions/improvements in v4.1
Date: Thu, 25 Jun 2015 10:30:07 +0100 [thread overview]
Message-ID: <20150625093007.GS7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150625091815.GR7557@n2100.arm.linux.org.uk>
On Thu, Jun 25, 2015 at 10:18:15AM +0100, Russell King - ARM Linux wrote:
> On Tue, Jun 23, 2015 at 09:50:00AM +0200, Geert Uytterhoeven wrote:
> As for the build errors you're reporting, that doesn't seem to be
> anything new. It seems to be down to a missing dependency between
> ARM_PTDUMP and MMU, which means that ARM_PTDUMP is selectable on !MMU
> systems. I'll add that dependency, but that's just a small drop in
> the ocean - it looks like it's the least of the problems with ARM
> randconfig...
Now that the build has finished... even with that fixed...
arch/arm/mach-versatile/built-in.o: In function `pci_versatile_setup':
arch/arm/mach-versatile/pci.c:249: undefined reference to `pci_ioremap_io'
kernel/built-in.o: In function `set_section_ro_nx':
kernel/module.c:1738: undefined reference to `set_memory_nx'
kernel/built-in.o: In function `set_page_attributes':
kernel/module.c:1709: undefined reference to `set_memory_ro'
...
which means that DEBUG_SET_MODULE_RONX also needs to depend on MMU.
As for the pci_ioremap_io, I'm not sure what to do about that.
In any case, I'll queue up both of these dependency fixes as low
priority. Thanks.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-06-25 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1435006096-12470-1-git-send-email-geert@linux-m68k.org>
2015-06-22 20:52 ` Build regressions/improvements in v4.1 Geert Uytterhoeven
2015-06-22 21:18 ` Russell King - ARM Linux
2015-06-23 7:50 ` Geert Uytterhoeven
2015-06-25 9:18 ` Russell King - ARM Linux
2015-06-25 9:30 ` Russell King - ARM Linux [this message]
2015-06-25 9:34 ` Russell King - ARM Linux
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=20150625093007.GS7557@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).