From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uboot-tools: pass empty CFLAGS on invocation of libfdt/setup.py
Date: Mon, 20 Mar 2017 22:57:42 +0100 [thread overview]
Message-ID: <20170320225742.054be334@free-electrons.com> (raw)
In-Reply-To: <1489768962-26768-1-git-send-email-jcmvbkbc@gmail.com>
Hello,
On Fri, 17 Mar 2017 09:42:42 -0700, Max Filippov wrote:
> When building u-boot tools in cross-build environment CFLAGS environment
> variable set up for target is taken into an account when building code
> for host. Make it empty on invocation of python.
>
> This fixes the following build errors when cross-compiling for xtensa:
>
> cc1: error: unrecognized command line option "-mlongcalls"
> cc1: error: unrecognized command line option "-mauto-litpools"
>
> Fixes:
> http://autobuild.buildroot.net/results/439d6dacfaa7f9244bd15ca04990c12a25ff4777
> http://autobuild.buildroot.net/results/e2fe36c20e75d01a01a6659ef11e888965a843b9
> http://autobuild.buildroot.net/results/6f37ff347822a76571a9fe9cf3c491fe7e4164fa
>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
There is still an issue with this:
http://autobuild.buildroot.net/results/eaf/eaf4e5ffc1b2dc3890c529f9d5a0d7e8b6813500/build-end.log
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-20 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 16:42 [Buildroot] [PATCH] uboot-tools: pass empty CFLAGS on invocation of libfdt/setup.py Max Filippov
2017-03-18 13:01 ` Thomas Petazzoni
2017-03-20 21:57 ` Thomas Petazzoni [this message]
2017-03-20 23:30 ` Max Filippov
2017-03-22 21:01 ` Thomas Petazzoni
2017-03-22 23:12 ` Max Filippov
2017-03-23 8:12 ` Arnout Vandecappelle
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=20170320225742.054be334@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.