From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to compile uboot v2012.10 on Buildroot 2016.05
Date: Fri, 1 Jul 2016 16:15:56 +0200 [thread overview]
Message-ID: <20160701161556.5e65b3df@free-electrons.com> (raw)
In-Reply-To: <1572014322.7513168.1467381657827.JavaMail.zimbra@datacom.ind.br>
Hello,
On Fri, 1 Jul 2016 11:00:57 -0300 (BRT), Carlos Santos wrote:
> > What is your host gcc version ? This failure smells like building an
> > old U-Boot, with gcc 5.x as the host gcc version.
>
> The problem happens on CentOS 7 (GCC 4.8.3) and Ubuntu 16.04 (GCC 5.3.1).
I think the failure with GCC 5.3.x is normal, but I don't understand
why it would fail with gcc 4.8.
> >> UBOOT_MAKE_OPTS += \
> >> CROSS_COMPILE="$(TARGET_CROSS)" \
> >> - ARCH=$(UBOOT_ARCH) \
> >> - HOSTCFLAGS="$(HOST_CFLAGS)" \
> >> - HOSTLDFLAGS="$(HOST_LDFLAGS)"
> >
> > I'm not sure to see why this would fix the problem you're reporting.
>
> It prevents overriding HOSTCFLAGS and HOSTLDFLAGS on targets that don't need OpenSSL, so older versions of U-Boot will compile successfully.
Yes, but I don't understand why not setting HOSTCFLAGS/HOSTLDFLAGS
fixes the build issue you mentioned.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-01 14: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 [this message]
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
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=20160701161556.5e65b3df@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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