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

On Thu, Jul 23, 2009 at 02:43:26PM +0200, Juan Quintela wrote:
> Jan Kiszka <jan.kiszka@siemens.com> wrote:
> >> -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.
> 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?

The particular instance was for detecting zlib in a cross
configuration.  But that's not necessarily the only test where
--extra-{cflags,ldflags} would be useful: every test that needs external
libraries is subject to this bug (zlib, TLS, SASL, SDL, VDE libraries,
BrlAPI?, Xen?, bluez?, etc.).

If adding EXTRA_{CFLAGS,LDFLAGS} to all such tests is necessary and
people feel that's the best solution, then I can do that.

-Nathan

  parent reply	other threads:[~2009-07-23 14:20 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 [this message]
     [not found]       ` <m33a8n5slq.fsf@neno.mitica>
2009-07-23 16:32         ` Jan Kiszka
2009-07-23 14:50     ` Jan Kiszka
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=20090723142002.GJ32566@codesourcery.com \
    --to=froydnj@codesourcery.com \
    --cc=jan.kiszka@siemens.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 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.