From: Will Deacon <will.deacon@arm.com>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [PATCH 1/2] Makefile: allow overriding CFLAGS on the command line
Date: Wed, 4 Nov 2015 10:49:58 +0000 [thread overview]
Message-ID: <20151104104957.GD5405@arm.com> (raw)
In-Reply-To: <CAAqcGHk=TMzmtAqAvy5q2XEkY0uf=49N-NX11BnSUv6zHfMwCw@mail.gmail.com>
On Wed, Nov 04, 2015 at 12:02:23PM +0200, Riku Voipio wrote:
> On 30 October 2015 at 19:20, Andre Przywara <andre.przywara@arm.com> wrote:
> > When a Makefile variable is set on the make command line, all
> > Makefile-internal assignments to that very variable are _ignored_.
> > Since we add quite some essential values to CFLAGS internally,
> > specifying some CFLAGS on the command line will usually break the
> > build (and not fix any include file problems you hoped to overcome
> > with that).
> > Somewhat against intuition GNU make provides the "override" directive
> > to change this behavior; with that assignments in the Makefile get
> > _appended_ to the value given on the command line. [1]
> >
> > Change any internal assignments to use that directive, so that a user
> > can use:
> > $ make CFLAGS=/path/to/my/include/dir
> > to teach kvmtool about non-standard header file locations (helpful
> > for cross-compilation) or to tweak other compiler options.
> >
> > Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> >
> > [1] https://www.gnu.org/software/make/manual/html_node/Override-Directive.html
> > ---
> > Makefile | 15 +++++++--------
> > 1 file changed, 7 insertions(+), 8 deletions(-)
> >
> > diff --git a/Makefile b/Makefile
> > index f8f7cc4..77a7c9f 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -15,9 +15,7 @@ include config/utilities.mak
> > include config/feature-tests.mak
> >
> > CC := $(CROSS_COMPILE)gcc
> > -CFLAGS :=
> > LD := $(CROSS_COMPILE)ld
> > -LDFLAGS :=
>
> This breaks builds of debian packages as dpkg-buildpackage sets LDFLAGS
> to something unsuitable for guest init.
Thanks for the report, Riku. I'll revert this patch while we rethink how
to support user-supplied toolchain flags.
Will
next prev parent reply other threads:[~2015-11-04 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 17:20 [PATCH 0/2] kvmtool: allow CFLAGS and LDFLAGS override Andre Przywara
2015-10-30 17:20 ` Andre Przywara
2015-10-30 17:20 ` [PATCH 1/2] Makefile: allow overriding CFLAGS on the command line Andre Przywara
2015-10-30 17:20 ` Andre Przywara
2015-11-04 10:02 ` Riku Voipio
2015-11-04 10:13 ` Andre Przywara
2015-11-04 10:27 ` Riku Voipio
2015-11-04 10:49 ` Will Deacon [this message]
2015-10-30 17:20 ` [PATCH 2/2] Makefile: consider LDFLAGS on feature tests and when linking executables Andre Przywara
2015-10-30 17:20 ` Andre Przywara
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=20151104104957.GD5405@arm.com \
--to=will.deacon@arm.com \
--cc=andre.przywara@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=riku.voipio@linaro.org \
/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.