qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michele Denber <mdenber@gmx.com>
To: eblake@redhat.com, qemu-devel@nongnu.org
Subject: Re: Building in Solaris 11.4
Date: Thu, 25 Jun 2020 14:32:36 -0400	[thread overview]
Message-ID: <5EF4EDC4.3030009@gmx.com> (raw)
In-Reply-To: <5EF4D332.6040003@gmx.com>

[-- Attachment #1: Type: text/plain, Size: 2260 bytes --]

Subject: 	Re: Building in Solaris 11.4
Date: 	Wed, 24 Jun 2020 16:48:51 -0500
From: 	Eric Blake <eblake@redhat.com>
Organization: 	Red Hat, Inc.
To: 	Michele Denber <mdenber@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



[-- Attachment #2: Type: text/html, Size: 4563 bytes --]

  parent reply	other threads:[~2020-06-25 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 21:31 Building in Solaris 11.4 Michele Denber
2020-06-24 21:48 ` Eric Blake
2020-06-24 21:53   ` Eric Blake
     [not found]   ` <5EF4D332.6040003@gmx.com>
2020-06-25 18:32     ` Michele Denber [this message]
2020-06-27 16:24 ` Michele Denber
2020-06-29 12:12   ` Thomas Huth
2020-06-29 20:25     ` Michele Denber
2020-06-30  5:10       ` Thomas Huth
  -- strict thread matches above, loose matches on Subject: below --
2020-06-27 21:19 Michele Denber
2020-06-28 13:22 ` Peter Maydell
2020-06-28 14:16   ` Peter Tribble

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=5EF4EDC4.3030009@gmx.com \
    --to=mdenber@gmx.com \
    --cc=eblake@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).