From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: barebox@lists.infradead.org
Subject: Commit "ARM: Turn most board directories into regular build directories" break kwb images
Date: Tue, 6 Aug 2013 11:49:45 +0200 [thread overview]
Message-ID: <20130806114945.065bda07@skate> (raw)
Hello Sascha,
Your commit 6bbb24cf8d0b0a060c57d9c07610210cdf2dcc96 ('ARM: Turn most
board directories into regular build directories') apparently breaks
the build of kwbimage for Marvell EBU platforms.
The kwbimage is built as follows:
KWBIMAGE_OPTS = \
-c -i $(srctree)/$(BOARD)/kwbimage.cfg -d $(TEXT_BASE) -e $(TEXT_BASE)
quiet_cmd_kwbimage = KWB $@
cmd_kwbimage = scripts/kwbimage -p $< $(KWBIMAGE_OPTS) -o $@ || \
echo "WARNING: Couldn't create KWB image due to previous errors."
quiet_cmd_kwbimage_uart = KWBUART $@
cmd_kwbimage_uart = scripts/kwbimage -m uart -p $< $(KWBIMAGE_OPTS) -o $@ || \
echo "WARNING Couldn't create KWB image due to previous errors."
so we rely on the $(BOARD) variable to contain
arch/arm/boards/<theboard>/. Unfortunately, with your commit, this is
no longer the case.
Your commit made the assumption that only those boards that have a
config.h should stay in board-y, but the Marvell EBU boards should also
stay in board-y, or another solution needs to be found.
I've temporarily worked around the problem by re-adding:
+board-$(CONFIG_MACH_GLOBALSCALE_GURUPLUG) += globalscale-guruplug
into arch/arm/Makefile.
Since I haven't yet grasped the entire philosophy of the Barebox build
system, I'm not sure what the correct fix is.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2013-08-06 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 9:49 Thomas Petazzoni [this message]
2013-08-06 11:50 ` Sascha Hauer
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=20130806114945.065bda07@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=barebox@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