From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5194] Fix the build on non-Linux systems
Date: Thu, 11 Sep 2008 13:17:26 -0500 [thread overview]
Message-ID: <48C960B6.1000806@codemonkey.ws> (raw)
In-Reply-To: <BAY110-DAV6AEC9D2636341001D0C0CB9560@phx.gbl>
C.W. Betts wrote:
> And it also doesn't link on 64-bit…
> I don't know what library has the sigwaitinfo call on it, nor do I
> know what headers define it. Spotlight only found one file,
> compatfd.c, and mail messages that reference it.
sigwaitinfo is part of POSIX. Is sigtimedwait() available? What about
just sigwait()?
Regards,
Anthony Liguori
> On Sep 11, 2008, at 10:33 AM, C.W. Betts wrote:
>
>> Actually, it builds in 10.5. Using the 10.4 SDK causes the problems.
>> On Sep 11, 2008, at 9:26 AM, C.W. Betts wrote:
>>
>>> Now it complains about missing symbols:
>>> Undefined symbols:
>>> "_sigwaitinfo", referenced from:
>>> _sigwait_compat in compatfd.o
>>> ld: symbol(s) not found
>>> collect2: ld returned 1 exit status
>>> make: *** [qemu-img] Error 1
>>> This happened both when trying to compile qemu-img and qemu-nbd.
>>> On Sep 11, 2008, at 8:18 AM, Anthony Liguori wrote:
>
prev parent reply other threads:[~2008-09-11 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 14:18 [Qemu-devel] [5194] Fix the build on non-Linux systems Anthony Liguori
[not found] ` <97371528-A47E-441F-87C7-66A30BAC42E0@hotmail.com>
2008-09-11 15:26 ` C.W. Betts
2008-09-11 16:06 ` Blue Swirl
2008-09-11 16:15 ` Anthony Liguori
2008-09-11 16:57 ` Blue Swirl
2008-09-11 16:20 ` Anthony Liguori
2008-09-11 17:06 ` Blue Swirl
[not found] ` <F63B4C90-4303-4A11-BF72-BF36682000FD@hotmail.com>
2008-09-11 16:33 ` C.W. Betts
[not found] ` <9E6E4065-F682-414C-AB68-A565A5BF2B07@hotmail.com>
2008-09-11 17:10 ` C.W. Betts
2008-09-11 18:17 ` Anthony Liguori [this message]
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=48C960B6.1000806@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).