From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] fbtest: Make its build-system aware of external CFLAGS and LDFLAGS
Date: Fri, 29 Jun 2012 16:02:30 +0200 [thread overview]
Message-ID: <20120629140230.GT10551@pengutronix.de> (raw)
In-Reply-To: <201206261541.50811.jbe@pengutronix.de>
On Tue, Jun 26, 2012 at 03:41:50PM +0200, Juergen Beisert wrote:
> Signed-off-by: Juergen Beisert <jbe@pengutronix.de>
>
> diff --git a/patches/fbtest-20041102-1/0006-Let-the-build-system-honor-external-defined-CFLAGS-a.patch
> b/patches/fbtest-20041102-1/0006-Let-the-build-system-honor-external-defined-CFLAGS-a.patch
> new file mode 100644
> index 0000000..7222ffe
> --- /dev/null
> +++ b/patches/fbtest-20041102-1/0006-Let-the-build-system-honor-external-defined-CFLAGS-a.patch
> @@ -0,0 +1,32 @@
> +From: Juergen Beisert <jbe@pengutronix.de>
> +Date: Tue, 26 Jun 2012 15:30:00 +0200
> +Subject: [PATCH] Let the build-system honor external defined CFLAGS and
> + LDFLAGS variables
> +
> +Signed-off-by: Juergen Beisert <jbe@pengutronix.de>
> +---
> + Rules.make | 4 ++--
> + 1 files changed, 2 insertions(+), 2 deletions(-)
> +
> +diff --git a/Rules.make b/Rules.make
> +index 5ef8cef..fb5a5b5 100644
> +--- a/Rules.make
> ++++ b/Rules.make
> +@@ -6,7 +6,7 @@ HOSTCC = gcc
> + IFLAGS = -I$(TOPDIR)/include
> + #DFLAGS = -g
> + OFLAGS = -O2 -fomit-frame-pointer
> +-CFLAGS = -Wall $(IFLAGS) $(DFLAGS) $(OFLAGS)
> ++CFLAGS += -Wall $(IFLAGS) $(DFLAGS) $(OFLAGS)
> +
> + SRCS += $(wildcard *.c)
> + OBJS += $(subst .c,.o,$(SRCS))
> +@@ -24,7 +24,7 @@ ifdef SUBDIRS
> + endif
> +
> + $(TARGET): $(OBJS)
> +- $(CC) -o $(TARGET) $(filter $(OBJS), $^) $(LIBS)
> ++ $(CC) -o $(TARGET) $(filter $(OBJS), $^) $(LIBS) $(LDFLAGS)
$(CC) $(LDFLAGS) -o $(TARGET) $(filter $(OBJS), $^) $(LIBS)
I think. I'm not sure it makes a difference here, but in general LDFLAGS
should come first.
Michael
> +
> + $(O_TARGET): $(OBJS)
> + $(LD) -r -o $(O_TARGET) $(filter $(OBJS), $^)
> diff --git a/patches/fbtest-20041102-1/series b/patches/fbtest-20041102-1/series
> index a820fe8..15055b3 100644
> --- a/patches/fbtest-20041102-1/series
> +++ b/patches/fbtest-20041102-1/series
> @@ -5,4 +5,5 @@
> 0003-Workaround-for-a-gcc-compiler-bug.patch
> 0004-remove-asm-page.h-use-sysconf.patch
> 0005-add-install-target.patch
> -# 9bb723ec368cacab6034723702d740a1 - git-ptx-patches magic
> +0006-Let-the-build-system-honor-external-defined-CFLAGS-a.patch
> +# 0c97af2d952319b97e339bee2423856b - git-ptx-patches magic
>
> --
> Pengutronix e.K. | Juergen Beisert |
> Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-06-29 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 13:41 Juergen Beisert
2012-06-29 14:02 ` Michael Olbrich [this message]
2012-06-29 14:37 ` Juergen Beisert
2012-06-29 14:44 ` [ptxdist] [PATCHv2] " Juergen Beisert
2012-06-29 15:32 ` Michael Olbrich
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=20120629140230.GT10551@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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