All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: Regressions in build process introduced since August
Date: Mon, 23 Nov 2020 19:17:39 +0100	[thread overview]
Message-ID: <ea9ec9fb-d4b3-16cd-0cb9-7aa13f60c638@weilnetz.de> (raw)
In-Reply-To: <06cdb8fb-7218-c197-30fa-261db68f5e2e@redhat.com>

Am 23.11.20 um 17:20 schrieb Paolo Bonzini:

> On 23/11/20 16:41, Daniel P. Berrangé wrote:
>>> Relying on pkg-config should be our strong preference. I expect 
>>> we're doing
>>> the old fashioned library check just for historical reasons, but 
>>> even RHEL-7
>>> supports pkg-config for libjpeg. So I think we're safe to just 
>>> unconditionally
>>> rely on pkg-config these days and thus have it "just work" for cross 
>>> compiles
>>> too.
>>
>> For that matter I think we can also rely on  pkg-config for sasl too, as
>> again all our supported platforms have a new enough cyrus-sasl to have
>> a pkg-config file present these days.
>
> Yes, I agree.  However we have at least -lmpathpersist that does not 
> have a pkg-config file.  In the meanwhile I'll integrate Stefan's 
> patch.  Stefan, is libjpeg the only one that is affected in your build 
> environment?
>
> Paolo
>

Yes, as far as I see currently only libjpeg is affected.

Thanks,
Stefan



  reply	other threads:[~2020-11-23 18:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15 10:57 Regressions in build process introduced since August Stefan Weil
2020-11-17 17:50 ` Stefano Garzarella
2020-11-17 18:01   ` Paolo Bonzini
2020-11-17 19:57     ` Stefan Weil
2020-11-21 10:25     ` Stefan Weil
2020-11-21 11:09       ` Stefan Weil
2020-11-21 11:25         ` Stefan Weil
2020-11-21 11:31           ` Paolo Bonzini
2020-11-23 13:55         ` Paolo Bonzini
2020-11-23 14:40           ` Stefan Weil
2020-11-23 15:28             ` Paolo Bonzini
2020-11-23 15:28             ` Daniel P. Berrangé
2020-11-23 15:41               ` Daniel P. Berrangé
2020-11-23 16:20                 ` Paolo Bonzini
2020-11-23 18:17                   ` Stefan Weil [this message]
2020-11-18 15:34 ` Daniel P. Berrangé
2020-11-18 19:50   ` Stefan Weil

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=ea9ec9fb-d4b3-16cd-0cb9-7aa13f60c638@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=berrange@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    /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.