From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: meson incorrectly detects libcurl as present even if it spots that its dependencies are missing
Date: Thu, 15 Apr 2021 15:06:31 +0200 [thread overview]
Message-ID: <c3e0214a-64ef-944c-d21a-87da6c71a2fa@redhat.com> (raw)
In-Reply-To: <CAFEAcA8xHxCGhh2hibsdCxZrYRRU+xcwVsa85O7KL9BsmW7ohw@mail.gmail.com>
On 4/15/21 2:29 PM, Peter Maydell wrote:
> My build of system-emulation with --enable-static seems to have
> broken at some point since the last time I had cause to run it.
Maybe a side-effect of commit d7dedf428fe tri-state?
("meson: accept either shared or static libraries if --disable-static")
> Looking at the meson-log the cause seems to be that meson enables
> libcurl support even though it has found that libcurl's dependencies
> aren't present as static libs:
>
> Determining dependency 'libcurl' with pkg-config executable
> '/usr/bin/pkg-config'
> PKG_CONFIG_PATH:
> Called `/usr/bin/pkg-config --modversion libcurl` -> 0
> 7.58.0
> PKG_CONFIG_PATH:
> Called `/usr/bin/pkg-config --cflags libcurl` -> 0
> -I/usr/include/x86_64-linux-gnu
> PKG_CONFIG_PATH:
> Called `/usr/bin/pkg-config libcurl --libs --static` -> 0
> -L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu/mit-krb5
> -lcurl -lnghttp2 -lidn2 -lrtmp -lpsl -lnettle -lgnutls
> -Wl,-Bsymbolic-functions -Wl,-z,relro -lgssapi_krb5 -lkrb5 -lk5crypto
> -lcom_err -llber -lldap -llber -lz
> PKG_CONFIG_PATH:
> Called `/usr/bin/pkg-config libcurl --libs --static` -> 0
> -L/usr/lib/x86_64-linux-gnu/mit-krb5 -lcurl -lnghttp2 -lidn2 -lrtmp
> -lpsl -lnettle -lgnutls -Wl,-Bsymbolic-functions -Wl,-z,relro
> -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -llber -lldap -llber -lz
> None of 'PKG_CONFIG_PATH' are defined in the environment, not changing
> global flags.
> WARNING: Static library 'nghttp2' not found for dependency 'libcurl',
> may not be statically linked
> WARNING: Static library 'psl' not found for dependency 'libcurl', may
> not be statically linked
> WARNING: Static library 'gssapi_krb5' not found for dependency
> 'libcurl', may not be statically linked
> WARNING: Static library 'krb5' not found for dependency 'libcurl', may
> not be statically linked
> WARNING: Static library 'k5crypto' not found for dependency 'libcurl',
> may not be statically linked
> Run-time dependency libcurl found: YES 7.58.0
>
>
> This seems wrong to me -- if meson is smart enough to spot that
> it's not actually going to be able to statically link libcurl
> because of all those missing static libs, it should determine that
> it has not found a working libcurl, rather than saying that it has
> and letting the build proceed until the final link of executables fails.
>
> thanks
> -- PMM
>
prev parent reply other threads:[~2021-04-15 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 12:29 meson incorrectly detects libcurl as present even if it spots that its dependencies are missing Peter Maydell
2021-04-15 13:06 ` Philippe Mathieu-Daudé [this message]
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=c3e0214a-64ef-944c-d21a-87da6c71a2fa@redhat.com \
--to=philmd@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).