From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] xen: Remove TARGET_CONFIGURE_OPTS from make
Date: Sat, 17 Sep 2016 16:44:13 +0200 [thread overview]
Message-ID: <20160917164413.5385d83f@free-electrons.com> (raw)
In-Reply-To: <20160917160947.1b29638d@free-electrons.com>
Hello,
On Sat, 17 Sep 2016 16:09:47 +0200, Thomas Petazzoni wrote:
> So apparently, the fact that we are passing our own CFLAGS confuses the
> Xen build system, which then adds its own CFLAGS twice for some reason.
Looking at the Xen Git history, this __OBJECT_FILE__ definition is new
in 4.7.0 and did not exist in 4.6.0. So, this "duplication" of CFLAGS
most likely already occurred with Xen 4.6.0, but was not noticed due to
the fact that all other options can be passed several times.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-17 14:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 20:45 [Buildroot] [PATCH 1/2] xen: Disable -Werror when building Alistair Francis
2016-09-13 20:45 ` [Buildroot] [PATCH 2/2] xen: Remove TARGET_CONFIGURE_OPTS from make Alistair Francis
2016-09-13 23:23 ` Arnout Vandecappelle
2016-09-17 14:09 ` Thomas Petazzoni
2016-09-17 14:44 ` Thomas Petazzoni [this message]
2016-09-19 18:41 ` Alistair Francis
2016-10-03 18:06 ` Alistair Francis
2016-10-22 21:18 ` Thomas Petazzoni
2016-10-24 7:19 ` Alistair Francis
2016-10-28 20:26 ` Alistair Francis
2016-10-29 14:43 ` [Buildroot] [PATCH] package/xen: fix build failure on x86 after bump to 47 Yann E. MORIN
2016-10-29 18:27 ` Yann E. MORIN
2016-10-31 22:06 ` Alistair Francis
2016-11-01 0:42 ` Alistair Francis
2016-11-01 8:37 ` Yann E. MORIN
2016-09-13 22:57 ` [Buildroot] [PATCH 1/2] xen: Disable -Werror when building Arnout Vandecappelle
2016-09-13 23:19 ` Arnout Vandecappelle
2016-09-19 16:18 ` Alistair Francis
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=20160917164413.5385d83f@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