On Fri, Nov 13, 2015 at 01:01:52PM +0000, Peter Maydell wrote: > On 13 November 2015 at 11:31, Daniel P. Berrange <berra...@redhat.com> wrote: > > Developers on 64-bit machines will often try to perform a > > 32-bit build of QEMU by running > > > > ./configure --extra-cflags="-m32" > > > > Unfortunately if PKG_CONFIG_LIBDIR is not set to point to > > the location of the 32-bit pkg-config files, then configure > > will silently pick up the 64-bit pkg-config files and still > > succeed. > > Will this also handle all the other -config programs that > seem to have sprouted up? Looking in configure we also call > sdl-config > sdl2-config > libgcrypt-config > aalib-config > curl-config
For custom non-pkg-config programs there's not any good general purpose solution for them to look for 32-bit versions while on 64-bit hosts, at least not when 32-bit and 64-bit are both installed into the same /usr prefix. If the 32-bit stuff is installed in a completely separate root prefix, then you can sometimes update $PATH to ensure the right -config binary is found. This is a good reason why libs are encouraged to switch to using pkg-config instead of home-grown alternatives 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 :|