From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] rpi_2 builds fine with make, fails with buildman
Date: Tue, 24 Feb 2015 09:51:56 -0700 [thread overview]
Message-ID: <54ECAC2C.6010306@wwwdotorg.org> (raw)
In-Reply-To: <20150224094833.2729ec26@lilith>
On 02/24/2015 01:48 AM, Albert ARIBAUD wrote:
> Hello,
>
> Can anyone confirm that on current u-boot/master, rpi_2 build fine with
>
> git clean -xfd; make rpi_2_defconfig; make
>
> but fails with
>
> tools/buildman/buildman rpi_2
>
> with the following error:
>
>> arm: + rpi_2
>> +make[3]: *** No rule to make target 'arch/arm/cpu/armv7/bcm2835/../../arm1176/bcm2835//init.o', needed by 'arch/arm/cpu/armv7/bcm2835/built-in.o'. Stop.
>> +make[2]: *** [arch/arm/cpu/armv7/bcm2835] Error 2
>> +make[1]: *** [arch/arm/cpu/armv7] Error 2
>> +make: *** [sub-make] Error 2
>
> My gut feeling is that the problem lies with the fact that
> arch/arm/cpu/armv7/bcm2835/ contains a Makefile which refers to
> init.o, reset.o, timer.o and mbox.o but the source code for these
> resides in another directory, arch/arm/cpu/arm1176/bcm2835/.
>
> CC:ing Stephen as directory arch/arm/cpu/armv7/bcm2835/ was introduced
> by his commit db75356f (committed by Tom, also cc:) and Simon, since
> the issue is related to buildman.
This problem exists with quite a few boards, including the rpi port
before the addition of rpi_2 support. It's a bit intermittent which may
be why you didn't notice before.
See the following, and replies:
http://lists.denx.de/pipermail/u-boot/2015-February/205255.html
next prev parent reply other threads:[~2015-02-24 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 8:48 [U-Boot] rpi_2 builds fine with make, fails with buildman Albert ARIBAUD
2015-02-24 16:51 ` Stephen Warren [this message]
2015-02-25 22:13 ` Albert ARIBAUD
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=54ECAC2C.6010306@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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