[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Libvirt / GNULIB failures using Mingw64 toolchain
From: |
Daniel P. Berrange |
Subject: |
Re: Libvirt / GNULIB failures using Mingw64 toolchain |
Date: |
Wed, 20 Jun 2012 10:36:06 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Wed, Jun 20, 2012 at 02:11:32AM +0200, Bruno Haible wrote:
> Daniel P. Berrange wrote:
> > > > CC stdio-read.lo
> > > > ../../../gnulib/lib/stdio-read.c:102:1: error: redefinition of 'vscanf'
> > > > In file included from ./stdio.h:43:0,
> > > > from ../../../gnulib/lib/stdio-read.c:21:
> > > > /usr/x86_64-w64-mingw32/sys-root/mingw/include/stdio.h:397:7: note:
> > > > previous definition of 'vscanf' was here
>
> Their <stdio.h> file now *defines* many functions:
> sscanf
> scanf
> fscanf
> vsscanf
> vscanf
> vfscanf
> fprintf
> printf
> sprintf
> vfprintf
> vprintf
> vsprintf
> asprintf
> vasprintf
> snprintf
> vsnprintf
> swscanf
> wscanf
> fwscanf
> vswscanf
> vwscanf
> vfwscanf
> fwprintf
> wprintf
> swprintf
> vfwprintf
> vwprintf
> vswprintf
> snwprintf
> vsnwprintf
>
> But the situation is not clear to me. What are the results of
> $ grep -i vscanf config.status
> $ grep STDIO config.status
> ?
Here's what i see in config.status for my libvirt build:
$ grep -i vscanf config.status
S["GNULIB_VSCANF"]="0"
$ grep STDIO config.status
S["NEXT_AS_FIRST_DIRECTIVE_STDIO_H"]="<stdio.h>"
S["NEXT_STDIO_H"]="<stdio.h>"
S["REPLACE_STDIO_WRITE_FUNCS"]="1"
S["REPLACE_STDIO_READ_FUNCS"]="1"
S["GNULIB_STDIO_H_SIGPIPE"]="1"
S["GNULIB_STDIO_H_NONBLOCKING"]="1"
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|