From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: vexpress compilation error in next-20121127
Date: Wed, 28 Nov 2012 12:36:04 +0000 [thread overview]
Message-ID: <1354106164.2987.21.camel@hornet> (raw)
In-Reply-To: <50B56601.5010305@broadcom.com>
On Wed, 2012-11-28 at 01:16 +0000, Markus Mayer wrote:
> Hi Pawel,
>
> There seems to be an issue compiling vexpress at this point. The problem
> being that vexpress' makefile references reset.o, but there's no reset.c
> in arch/arm/mach-vexpress.
>
> [...]
> CC arch/arm/mach-bcm/board_bcm.o
> LD arch/arm/mach-bcm/built-in.o
> CC arch/arm/mach-vexpress/v2m.o
> make[1]: *** No rule to make target `arch/arm/mach-vexpress/reset.o',
> needed by `arch/arm/mach-vexpress/built-in.o'. Stop.
> make: *** [arch/arm/mach-vexpress] Error 2
>
> The commit in question seems to be this:
>
> http://git.kernel.org/?p=linux/kernel/git/arm/arm-soc.git;a=commitdiff;h=38669e045dbf8f62a008898a7fb1e93975b3817c
>
> It adds the reference to reset.o to the makefile, but doesn't add
> reset.c itself. That doesn't seem right -- or did I overlook anything
> obvious?
That's strange... The reset.c comes from the vexpress/drivers branch,
which seems to be merged correctly in the arm-soc:
http://git.kernel.org/?p=linux/kernel/git/arm/arm-soc.git;a=tree;f=arch/arm/mach-vexpress;hb=refs/heads/for-next
And it's there in the linux-next head:
https://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=tree;f=arch/arm/mach-vexpress
Also the next-20121127 looks good for me:
https://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=tree;f=arch/arm/mach-vexpress;h=47f9de5972efaa719c35bb9dce177fbd2954647c;hb=ce2931ab5e448a93fee55d9d82de9f5e754ff6f7
Are you sure you've checked out the correct tag?
Pawe?
next prev parent reply other threads:[~2012-11-28 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 1:16 vexpress compilation error in next-20121127 Markus Mayer
2012-11-28 12:36 ` Pawel Moll [this message]
2012-11-28 20:53 ` Markus Mayer
2012-11-29 11:39 ` Pawel Moll
2012-11-29 20:03 ` Markus Mayer
2012-12-13 19:07 ` Behan Webster
2012-12-14 9:49 ` Pawel Moll
2012-12-14 14:47 ` Behan Webster
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=1354106164.2987.21.camel@hornet \
--to=pawel.moll@arm.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 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.