From: Thomas Huth <thuth@redhat.com>
To: Owen LaGarde <olagarde@gmail.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: configure --extra-cflags and --extra-ldflags values not propagating to meson?
Date: Mon, 25 Oct 2021 15:10:07 +0200 [thread overview]
Message-ID: <a105f305-b1e8-f97a-fa09-f083190e34cb@redhat.com> (raw)
In-Reply-To: <CACDcNnWWbzkH5-h6=BoXdA92DyVfTD7Kp=Spoz62yXw5t+tLGw@mail.gmail.com>
On 22/10/2021 13.20, Owen LaGarde wrote:
> Am I using --extra-cflags and --extra-ldflags wrong in the configure call?
>
> I'd like to source build several pre-reqs specific to supporting the qemu source
> build. I'd specifically not like to install neither the qemu or re-req builds
> at the system level. Normally I'd expect the --extra-cflags and --extra-ldflags
> configure options to do this but they do not appear to propagate to meson.
> There
> was an approved meson patch back in 2018 for extra-cflags / extra-ldflags
> and qemu
> is currently using meson >5.8(?) but it doesn't look like configure is
> adding the
> args anywhere in the build tree. There are a number of ways to do this, what's
> appropriate / future-proof wrt building qemu from source? And why is configure
> supporting --extra-[c,ld]args but not doing anything with the values?
I see a similar behavior with netmap now - I've got the corresponding header
file in a non-standard directory, and up to commit 837b84b1c078bf3e909 it
used to work fine to do:
.../configure --enable-netmap \
--extra-cflags=-I/path/to/netmap/sys
but since the conversion to meson, this does not seem to work anymore.
Paolo, any ideas?
Thomas
PS: As a work-around, it seems to be fine to pass the flags via the CFLAGS
environment variable instead:
CFLAGS=-I/path/to/netmap/sys .../configure --enable-netmap
next prev parent reply other threads:[~2021-10-25 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 11:20 configure --extra-cflags and --extra-ldflags values not propagating to meson? Owen LaGarde
2021-10-25 13:10 ` Thomas Huth [this message]
2021-10-25 17:26 ` Paolo Bonzini
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=a105f305-b1e8-f97a-fa09-f083190e34cb@redhat.com \
--to=thuth@redhat.com \
--cc=olagarde@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).