qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Juan Quintela <quintela@trasno.org>
Cc: qemu-devel@nongnu.org, Nathan Froyd <froydnj@codesourcery.com>
Subject: [Qemu-devel] Re: [PATCH] configure: fix breakage of --extra-{cflags, ldflags}
Date: Thu, 23 Jul 2009 16:50:20 +0200	[thread overview]
Message-ID: <4A6878AC.1080305@siemens.com> (raw)
In-Reply-To: <m3bpnb6041.fsf@neno.mitica>

Juan Quintela wrote:
> Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> Nathan Froyd wrote:
>>> Commit e3fc14c3a1a77a1cda669a3e16f1f6b82577e4ec broke the use of
>>> --extra-{cflags,ldflags} in the case where those flags were necessary
>>> for bits of configure to succeed.  For instance, if you did:
>>>
>>>   configure [...] --extra-cflags=-I/path/to/zlib/headers \
>>>     --extra-ldflags=-L/path/to/zlib/libraries
>>>
>>> prior to the above commit, the paths would go into CFLAGS and LDFLAGS
>>> for use by the rest of the configure tests.  After the above commit,
>>> that's no longer true, because the EXTRA_{CFLAGS,LDFLAGS} variables are
>>> only used for creating makefiles.
>> Yep, that's true...
>>
>>> Fixed by making sure that EXTRA_{CFLAGS,LDFLAGS} find their way into
>>> {CFLAGS,LDFLAGS}, respectively.
>>>
>>> Signed-off-by: Nathan Froyd <froydnj@codesourcery.com>
>>> ---
>>>  configure |    4 ++--
>>>  1 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/configure b/configure
>>> index 0db885b..dd2b1d9 100755
>>> --- a/configure
>>> +++ b/configure
>>> @@ -520,8 +520,8 @@ CFLAGS="$CFLAGS -g -fno-strict-aliasing"
>>>  if test "$debug" = "no" ; then
>>>    CFLAGS="$CFLAGS -O2"
>>>  fi
>>> -CFLAGS="$CFLAGS -Wall -Wundef -Wendif-labels -Wwrite-strings -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls"
>>> -LDFLAGS="$LDFLAGS -g"
>>> +CFLAGS="$CFLAGS $EXTRA_CFLAGS -Wall -Wundef -Wendif-labels -Wwrite-strings -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls"
>>> +LDFLAGS="$LDFLAGS $EXTRA_LDFLAGS -g"
>> ...but now we add the extra flags twice. So please remove the injection
>> into the flags for $config_mak.
> 
> It is still broken.  Thinking of a solution.

Good that someone is more awake than /me. :)

> People wanted EXTRA_CFLAGS to be added at the end of CFLAGS, not in the
> middle.  Trying to find a way that is consistent for everything.
> 
> Could you told in what test do you need extra_cflags?

I think the only consistent solution (besides stopping to re-invent
autotools) is explicitly appending EXTRA_CFLAGS to all tests.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2009-07-23 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 11:40 [Qemu-devel] [PATCH] configure: fix breakage of --extra-{cflags, ldflags} Nathan Froyd
2009-07-23 14:13 ` [Qemu-devel] " Jan Kiszka
     [not found]   ` <m3bpnb6041.fsf@neno.mitica>
2009-07-23 14:20     ` Nathan Froyd
     [not found]       ` <m33a8n5slq.fsf@neno.mitica>
2009-07-23 16:32         ` Jan Kiszka
2009-07-23 14:50     ` Jan Kiszka [this message]
2009-07-23 16:58 ` [Qemu-devel] " Nathan Froyd

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=4A6878AC.1080305@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=froydnj@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@trasno.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 NNTP newsgroup(s).