All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Win2k host problem with {get, free}{addr, name}info()
Date: Wed, 22 Sep 2010 08:42:04 -0500	[thread overview]
Message-ID: <4C9A07AC.9070603@codemonkey.ws> (raw)
In-Reply-To: <4C9A073A.2050009@redhat.com>

On 09/22/2010 08:40 AM, Paolo Bonzini wrote:
> On 09/21/2010 08:32 PM, Blue Swirl wrote:
>> Sort of, gnulib needs some configuration before use. I made some hacks
>> to avoid that and also suppressed warnings by overriding QEMU_CFLAGS,
>> but it's getting ugly.
>>
>> Actually, there's no 'configure' in gnulib HEAD even though
>> docs/INSTALL mentions that. Strange.
>
> gnulib's docs/INSTALL is a template for packages using autotools, it's 
> not for gnulib itself.
>
>> Is it possible to apply local patches to a submodule tree?
>
> It is not needed; to explain this, you need to go one step back.
>
> gnulib's submodule is never built directly.  It only lives in the 
> build tree so that it can be consulted by gnulib-tool, but it doesn't 
> even make it to the release tarballs.  Instead, gnulib-tool should be 
> invoked after checking out superproject.git, and copies selected 
> gnulib files into superproject's checkout (these files are .gitignore'd).
>
> Now, gnulib-tool also take care of applying patches to the files it 
> copies, so the correct question is "is it possible to apply local 
> patches to gnulib files" and the answer is "yes".
>
> That said, as much as I am a fan of autotools, I think using gnulib 
> within qemu would be a big mess.

If someone was willing to put in the effort, I'd be very supportive of 
moving QEMU to autotools.

Regards,

Anthony Liguori

> Paolo

  reply	other threads:[~2010-09-22 13:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 19:11 [Qemu-devel] Win2k host problem with {get,free}{addr,name}info() Blue Swirl
2010-09-15 19:25 ` Anthony Liguori
2010-09-19 16:16   ` Blue Swirl
2010-09-20 18:26     ` Anthony Liguori
2010-09-20 18:41       ` Blue Swirl
2010-09-20 20:03         ` Blue Swirl
2010-09-20 20:21           ` Anthony Liguori
2010-09-21 18:32             ` Blue Swirl
2010-09-21 19:06               ` Anthony Liguori
2010-09-22 17:36                 ` Blue Swirl
2010-09-22 13:40               ` [Qemu-devel] Re: Win2k host problem with {get, free}{addr, name}info() Paolo Bonzini
2010-09-22 13:40               ` Paolo Bonzini
2010-09-22 13:42                 ` Anthony Liguori [this message]
2010-09-22 14:04                   ` Paolo Bonzini
2010-09-22 15:27                   ` malc
2010-09-22 16:36                     ` Paolo Bonzini
2010-09-22 16:38                       ` malc
2010-09-22 16:53                     ` Anthony Liguori
2010-09-22 17:16                 ` Blue Swirl
2010-09-23 11:22                   ` Paolo Bonzini
2010-09-21  8:09           ` Paolo Bonzini
2010-09-21  9:49             ` Bastien ROUCARIES
2010-09-20  4:16   ` [Qemu-devel] Win2k host problem with {get,free}{addr,name}info() Joe Ross
2010-09-20 17:56     ` Blue Swirl

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=4C9A07AC.9070603@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=blauwirbel@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 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.