Subject: Re: Building in Solaris 11.4
Date: Wed, 24 Jun 2020 16:48:51 -0500
From: Eric Blake <ebl...@redhat.com>
Organization: Red Hat, Inc.
To: Michele Denber <mden...@gmx.com>, qemu-devel@nongnu.org
As a short-term workaround, you can always do:
/path/to/bash ./configure
Ah yes, thank you. I now recall having that problem building 2.12 in
Solaris 10 a few years ago. The default bash in Solaris 11.4 is
/usr/bin/bash and that won't work. I used /opt/csw/bin/bash instead and
that took care of the "local" problem.
Similarly, the default Solaris grep is missing the -e option so I
changed grep to ggrep in configure. POSIX was always problematic in
Solaris because, I believe of Sun's efforts to maintain backward
compatibility.
So now I've got:
root@hemlock:~/qemu-5.0.0# /opt/csw/bin/bash ./configure --cc=gcc
ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
You probably need to set PKG_CONFIG_LIBDIR
to point to the right pkg-config files for your
build target
root@hemlock:~/qemu-5.0.0#
I fixed that by saying
# LD_LIBRARY_PATH
=/usr/openwin/lib:opt/csw/lib:/usr/local/lib:/lib:/opt/sfw/lib:/opt/csw/gxx/lib:/usr/X11/lib
#
PKG_CONFIG_PATH=/opt/csw/lib/pkgconfig:/usr/local/lib/pkgconfig:/opt/sfw/lib/pkgconfig:/usr/lib/pkgconfig
#
PKG_CONFIG_LIBDIR=/opt/csw/lib/pkgconfig:/usr/local/lib/pkgconfig:/opt/sfw/lib/pkgconfig:/usr/lib/pkgconfig
# /opt/csw/bin/bash ./configure --cc=gcc --extra-cflags="-m32"
(Thankfully I still have some notes from building QEMU 2.12.)
That gave me a successful configure ending with:
The QEMU project intends to remove support for this host OS in
a future release if nobody volunteers to maintain it and to
provide a build host for our continuous integration setup.
configure has succeeded and you can continue to build, but
if you care about QEMU on this platform you should contact
us upstream at qemu-devel@nongnu.org.
So I hereby volunteer. I have an 8 core 64 thread 2.85 GHz. Sun T4-1
with 64 GB and three 900 GB disks and a 500 MB/50 MB fiber Internet
connection..
Anyway, that's enough for one day. On to the gmake. I'm sure I'll have
more questions soon :-)
- Michele
