From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kevin Du Huanpeng <u74147@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: compile bug about banner and version macros.
Date: Wed, 16 Sep 2015 07:27:51 +0200 [thread overview]
Message-ID: <20150916052751.GC4018@pengutronix.de> (raw)
In-Reply-To: <CANvTkNYaWMG0biCUXs+hZNBoPBg6dvS8artP8eo+5pvU_MGSdg@mail.gmail.com>
On Tue, Sep 15, 2015 at 07:49:15PM +0800, Kevin Du Huanpeng wrote:
> this patch fix a tiny compile bug.
> 1. how to reproduce the bug.
> $ export ARCH=mips
> $ export CROSS_COMPILE=mips-linux-gnu-
> $ make allnoconfig
> - - - error msg - - -
> du@L64:~/source/barebox$ make
> CHK include/generated/version.h
> CHK include/generated/utsrelease.h
> AS arch/mips/boot/start.o
> arch/mips/boot/start.S:25:31: fatal error: generated/compile.h: No
> such file or directory
> #include <generated/compile.h>
> ^
> compilation terminated.
> make[1]: *** [arch/mips/boot/start.o] Error 1
> make: *** [arch/mips/boot] Error 2
include/generated/compile.h is autogenerated, but arch/mips/boot/start.o
does not have a dependency on that file, so depending on the number of
cores you have it might or might not exist when you compile start.S.
Just try building barebox again when it failed, it should work the
second time. The patch you post may work by accident, but is no proper
fix for this problem. Unfortunately I haven't found a working solution
yet other than removing UTS_VERSION from start.S
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-09-16 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 11:49 Kevin Du Huanpeng
2015-09-15 12:09 ` Kevin Du Huanpeng
2015-09-16 5:27 ` Sascha Hauer [this message]
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=20150916052751.GC4018@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=u74147@gmail.com \
/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