From: Ian Campbell <ijc@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] tools-only build broken
Date: Sat, 30 Aug 2014 01:04:47 +0100 [thread overview]
Message-ID: <1409357087.21481.75.camel@hellion.org.uk> (raw)
In-Reply-To: <1409342852.21481.73.camel@hellion.org.uk>
On Fri, 2014-08-29 at 21:07 +0100, Ian Campbell wrote:
> The tools-only target is currently broken:
> $ make CROSS_COMPILE=arm-linux-gnueabihf- tools-only
> CHK include/config/uboot.release
> /bin/sh: 1: cannot open include/config/auto.conf: No such file
> Makefile:1052: recipe for target 'include/config/uboot.release' failed
> make: *** [include/config/uboot.release] Error 2
>
> This is because tools-only depends on $(version_h), depends on
> include/config/uboot.release, depends include/config/auto.conf. I think
> this is all due to the support for LOCALVERSION(_AUTO).
>
> I'm not sure how to reconcile this, since the version stuff
> fundamentally needs the .config. Perhaps sandbox could be used?
In the meantime "touch include/config/auto.conf" lets it build (hardly
ideal though!)
Ian.
next prev parent reply other threads:[~2014-08-30 0:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 20:07 [U-Boot] tools-only build broken Ian Campbell
2014-08-30 0:04 ` Ian Campbell [this message]
2014-08-30 9:40 ` Matwey V. Kornilov
2014-08-31 2:44 ` Ian Campbell
2014-09-01 4:54 ` Simon Glass
2014-09-02 9:22 ` Ian Campbell
2014-09-02 19:19 ` Simon Glass
2014-09-02 21:44 ` Otavio Salvador
2014-09-02 23:14 ` Simon Glass
2014-09-03 1:44 ` Otavio Salvador
2014-09-03 1:46 ` Simon Glass
2014-09-03 2:20 ` Otavio Salvador
2014-09-03 9:25 ` Marek Vasut
2014-10-16 18:24 ` Otavio Salvador
2014-10-16 22:17 ` Marek Vasut
2014-10-17 15:35 ` Otavio Salvador
2014-10-17 15:46 ` Marek Vasut
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=1409357087.21481.75.camel@hellion.org.uk \
--to=ijc@hellion.org.uk \
--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