From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to compile uboot v2012.10 on Buildroot 2016.05
Date: Sun, 3 Jul 2016 13:15:08 -0300 (BRT) [thread overview]
Message-ID: <170867641.7742576.1467562508600.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20160702125625.11882f51@free-electrons.com>
> From: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
> To: "Arnout Vandecappelle" <arnout@mind.be>
> Cc: "Carlos Santos" <casantos@datacom.ind.br>, "Julien Boibessot" <julien.boibessot@armadeus.com>, "buildroot"
> <buildroot@buildroot.org>
> Sent: Saturday, July 2, 2016 7:56:25 AM
> Subject: Re: [Buildroot] Unable to compile uboot v2012.10 on Buildroot 2016.05
> Hello,
>
> On Sat, 2 Jul 2016 12:47:14 +0200, Arnout Vandecappelle wrote:
>
>> > Because the value of HOSTCFLAGS set in U-Boot's config.mk is overwritten.
>>
>> How about leaving HOSTCFLAGS alone, and instead setting
>> HOSTCC="$(HOSTCC) $(HOST_CFLAGS)". HOSTLDFLAGS can probably be overridden.
>
> Good point, that's possibly an alternate solution. I sent a patch
> implementing a different solution, but Carlos, if you can try Arnout's
> suggestion, it would be good.
Yes, it works, but this reminds me that HOSTCC is not passed when building buildroot, so the command line for version 2015.01 becomes
cc -Wp,-MD,tools/.img2srec.d -O2 -I/work/freescale_imx28evk/host/usr/include -include ./include/libfdt_env.h -idirafterinclude -idirafter./arch/arm/include -I./lib/libfdt -I./tools -DCONFIG_SYS_TEXT_BASE=0x40002000 -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE -pedantic -o tools/img2srec tools/img2srec.c
This may not be a problem now but I believe that HOSTCC should always be provided.
Carlos Santos (Casantos)
DATACOM, P&D
next prev parent reply other threads:[~2016-07-03 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 13:10 [Buildroot] Unable to compile uboot v2012.10 on Buildroot 2016.05 Carlos Santos
2016-07-01 13:18 ` Thomas Petazzoni
2016-07-01 14:00 ` Carlos Santos
2016-07-01 14:15 ` Thomas Petazzoni
2016-07-01 15:28 ` Carlos Santos
2016-07-02 10:47 ` Arnout Vandecappelle
2016-07-02 10:56 ` Thomas Petazzoni
2016-07-03 16:15 ` Carlos Santos [this message]
2016-07-04 9:26 ` Arnout Vandecappelle
2016-07-04 11:15 ` Carlos Santos
2016-07-05 9:10 ` Arnout Vandecappelle
2016-07-01 16:22 ` Stephen Agate
[not found] <7524b7ea-7075-0058-8167-3fbc0051f2da@talktalk.net>
2016-07-01 19:44 ` Carlos Santos
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=170867641.7742576.1467562508600.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--cc=buildroot@busybox.net \
/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