On Wed, Sep 22, 2010 at 1:40 PM, Paolo Bonzini <pbonz...@redhat.com> 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).
gnulib-tool wants to patch configure.ac. After adding an empty one and running "gnulib-tool --import getaddrinfo inet_ntop", it still remains empty. Not very clever. There are a lot of .c files, some .h files and also a lot of .m4 files. I think we want to avoid this path.
