trinity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markos Chandras <markos.chandras@imgtec.com>
To: trinity@vger.kernel.org
Cc: Markos Chandras <markos.chandras@imgtec.com>
Subject: [PATCH 1/2] configure.sh: Respect CFLAGS from the environment
Date: Fri, 19 Sep 2014 15:11:54 +0100	[thread overview]
Message-ID: <1411135915-26522-2-git-send-email-markos.chandras@imgtec.com> (raw)
In-Reply-To: <1411135915-26522-1-git-send-email-markos.chandras@imgtec.com>

Currently, configure.sh does not inherit any cflags from the
environment. However, for MIPS, it's necessary to pass additional
cflags to decide, for example, if we want a big endian (-BE) or
little endian (-EL) build. As a result of which, we modify the
configure.sh script to respect additional cflags passed by the
user.

Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
---
 configure.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/configure.sh b/configure.sh
index d2a31c266519..98905fb8e7fd 100755
--- a/configure.sh
+++ b/configure.sh
@@ -16,9 +16,9 @@ MISSING_DEFS=0
 # expand tilde
 CC="$(eval echo ${CROSS_COMPILE}${CC})"
 
-CFLAGS=""
+CFLAGS="${CFLAGS}"
 if [ "${SYSROOT}xx" != "xx" ]; then
-	CFLAGS="$(eval echo --sysroot=${SYSROOT} )"
+	CFLAGS="${CFLAGS} $(eval echo --sysroot=${SYSROOT} )"
 fi
 
 echo "#pragma once" > $CONFIGH
-- 
2.1.0

  reply	other threads:[~2014-09-19 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 14:11 [PATCH 0/2] Small MIPS fixes Markos Chandras
2014-09-19 14:11 ` Markos Chandras [this message]
2014-09-19 14:11 ` [PATCH 2/2] maps: Rename MAP_{GLOBAL, LOCAL} to TRINITY_MAP_{GLOBAL, LOCAL} Markos Chandras
2014-09-22 13:37 ` [PATCH 0/2] Small MIPS fixes Dave Jones
2014-09-22 13:42   ` Markos Chandras

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=1411135915-26522-2-git-send-email-markos.chandras@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=trinity@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).