All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH 13/21] Build system: Always append CFLAGS at the end
Date: Tue, 3 Jan 2012 11:22:28 +0000	[thread overview]
Message-ID: <4F02E4F4.9090707@imgtec.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 49 bytes --]

Hi, please review the attached patch

-- 
markos

[-- Attachment #2: 0013-Build-system-Always-append-CFLAGS-at-the-end.patch --]
[-- Type: text/plain, Size: 1260 bytes --]

From 5800c95986bb1d63ef0af9dda4eb87c771bcccf3 Mon Sep 17 00:00:00 2001
From: Markos Chandras <markos.chandras@imgtec.com>
Date: Thu, 22 Dec 2011 17:22:48 +0000
Subject: [PATCH 13/21] Build system: Always append CFLAGS at the end

The build system sets -g -O2 -fno-strict-aliasing -pipe by default. We
append the enviromental CFLAGS at the end to allow the user to override
the default CFLAGS

Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
---
 include/mk/config.mk.in |    7 +++++--
 1 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/include/mk/config.mk.in b/include/mk/config.mk.in
index b835c86..6148b2c 100644
--- a/include/mk/config.mk.in
+++ b/include/mk/config.mk.in
@@ -72,8 +72,11 @@ WCFLAGS			?= -Wall
 WCXXFLAGS		?= $(WCFLAGS)
 
 LDFLAGS			+= $(WLDFLAGS)
-CFLAGS			+= $(DEBUG_CFLAGS) $(OPT_CFLAGS) $(WCFLAGS)
-CXXFLAGS		+= $(DEBUG_CXXFLAGS) $(OPT_CXXFLAGS) $(WCXXFLAGS)
+AMCFLAGS		= $(DEBUG_CFLAGS) $(OPT_CFLAGS) $(WCFLAGS) $(CFLAGS)
+AMCXXFLAGS		= $(DEBUG_CXXFLAGS) $(OPT_CXXFLAGS) $(WCXXFLAGS) $(CXXFLAGS)
+
+CFLAGS			:= $(AMCFLAGS)
+CXXFLAGS		:= $(AMCXXFLAGS)
 
 ifeq ($(strip $(prefix)),)
 $(error you are using $$(prefix) incorrectly -- set it to $(abs_top_srcdir) if you want to build in the source tree)
-- 
1.7.1


[-- Attachment #3: Type: text/plain, Size: 355 bytes --]

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2012-01-03 11:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 11:22 Markos Chandras [this message]
2012-01-03 19:47 ` [LTP] [PATCH 13/21] Build system: Always append CFLAGS at the end Garrett Cooper

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=4F02E4F4.9090707@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=ltp-list@lists.sourceforge.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.