qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] build-sys: remove slirp cflags from main-loop.o
Date: Fri, 12 Jul 2019 19:49:40 +0200	[thread overview]
Message-ID: <53fb3e82-ba72-e987-0fdf-160c0070a274@redhat.com> (raw)
In-Reply-To: <CAJ+F1CK2wgSsmFFnrhdRKh-pFh-JK5Ov3t34hVf2cB6THpYv0Q@mail.gmail.com>

On 12/07/19 19:46, Marc-André Lureau wrote:
> Hi
> 
> On Fri, Jul 12, 2019 at 9:37 PM Philippe Mathieu-Daudé
> <philmd@redhat.com> wrote:
>>
>> Hi Marc-André,
>>
>> On 7/12/19 7:27 PM, Marc-André Lureau wrote:
>>> Left over from c2d63650d962612cfa1b21302782d4cd12142c74.
>>>
>>> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>
>>> ---
>>>  util/Makefile.objs | 1 -
>>>  1 file changed, 1 deletion(-)
>>>
>>> diff --git a/util/Makefile.objs b/util/Makefile.objs
>>> index 38178201ff..68af3cd5e9 100644
>>> --- a/util/Makefile.objs
>>> +++ b/util/Makefile.objs
>>> @@ -3,7 +3,6 @@ util-obj-y += bufferiszero.o
>>>  util-obj-y += lockcnt.o
>>>  util-obj-y += aiocb.o async.o aio-wait.o thread-pool.o qemu-timer.o
>>>  util-obj-y += main-loop.o iohandler.o
>>> -main-loop.o-cflags := $(SLIRP_CFLAGS)
>>>  util-obj-$(call lnot,$(CONFIG_ATOMIC64)) += atomic64.o
>>>  util-obj-$(CONFIG_POSIX) += aio-posix.o
>>>  util-obj-$(CONFIG_POSIX) += compatfd.o
>>>
>>
>> Since you are looking at slirp, I'm having a bunch of:
>>
>> $ make help
>> [...]
>>   CC      slirp/src/tftp.o
>> Package glib-2.0 was not found in the pkg-config search path.
>> Perhaps you should add the directory containing `glib-2.0.pc'
>> to the PKG_CONFIG_PATH environment variable
>> No package 'glib-2.0' found
>>   CC      slirp/src/udp6.o
>> Package glib-2.0 was not found in the pkg-config search path.
>> Perhaps you should add the directory containing `glib-2.0.pc'
>> to the PKG_CONFIG_PATH environment variable
>> No package 'glib-2.0' found
>> [...]
>>
>> On MinGW.
> 
> On "cross-mingw" I suppose
> 
>> I can silent the warnings using (32-git build):
>>
>> PKG_CONFIG_PATH=/usr/lib/mxe/usr/i686-w64-mingw32.shared/lib/pkgconfig
> 
> Hmm that looks like a pkg-config configuration issue to me.
> 
>>
>> This is new since the slirp split.
>>
>> Any idea where to fix that?
>>
> 
> Compile and install libslirp shared lib, ./configure --enable-slirp=system :)
> 
> Btw, I wonder if we can already warn about deprecation of
> --enable-slirp=git. Peter is that too early for 4.1? (first libslirp
> was released last month)

Yeah, I think we should let a year pass or so.

Paolo



      reply	other threads:[~2019-07-12 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 17:27 [Qemu-devel] [PATCH] build-sys: remove slirp cflags from main-loop.o Marc-André Lureau
2019-07-12 17:33 ` Paolo Bonzini
2019-07-12 17:37 ` Philippe Mathieu-Daudé
2019-07-12 17:46   ` Marc-André Lureau
2019-07-12 17:49     ` Paolo Bonzini [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=53fb3e82-ba72-e987-0fdf-160c0070a274@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@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).