qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michele Denber <mdenber@gmx.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Peter Tribble <peter.tribble@gmail.com>
Subject: Re: Building in Solaris 11.4
Date: Mon, 29 Jun 2020 16:25:42 -0400	[thread overview]
Message-ID: <5EFA4E46.3090101@gmx.com> (raw)
In-Reply-To: <fcdd4b6c-eec5-2bfd-1004-8ac86e80bf0e@redhat.com>

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

On 06-29-2020 8:12 AM, Thomas Huth wrote:
> ...
> It's not the same bug as last year, but a new one: Seems like newer
> versions of Solaris now have this functions in their libraries!
Yes - I just checked. Solaris 10 does not have openpty, but Solaris 11.4
indeed does have it
> So what you want is something like this (completely untested):

So just to make sure I have this right - I save that code into a patch
file and then apply it where?  At the qemu-5.0.0 level?  Then run
configure again?

Right now I'm looking at that "struct dirent" problem in gmake I
mentioned a few days ago.  I will try the Haiku patch offered by PMM.

             - MIchele


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

  reply	other threads:[~2020-06-29 20:29 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
2020-06-27 16:24 ` Michele Denber
2020-06-29 12:12   ` Thomas Huth
2020-06-29 20:25     ` Michele Denber [this message]
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=5EFA4E46.3090101@gmx.com \
    --to=mdenber@gmx.com \
    --cc=peter.maydell@linaro.org \
    --cc=peter.tribble@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).