From: Alexander Graf <alex@csgraf.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Mac OS X build failure (qemu-img)
Date: Wed, 12 Dec 2007 13:08:20 +0100 [thread overview]
Message-ID: <AE59A20B-5EBA-4F12-BFA7-4C3C7BA25E4C@csgraf.de> (raw)
In-Reply-To: <D475D0A0-7F43-463D-B2EB-4F49962BB1F8@web.de>
On Dec 12, 2007, at 12:39 PM, Andreas Färber wrote:
>
> Am 11.11.2007 um 13:40 schrieb Andreas Färber:
>
>> Building CVS HEAD on OS X (here sparc-softmmu) currently results in
>> unresolved symbols:
>>
>> gcc-3.3 -g -o qemu-img qemu-img.o qemu-img-block.o qemu-img-
>> block-raw.o cutils.o block-cow.o block-qcow.o aes.o block-vmdk.o
>> block-cloop.o block-dmg.o block-bochs.o block-vpc.o block-vvfat.o
>> block-qcow2.o block-parallels.o -lz
>> ld: Undefined symbols:
>> _CFDictionarySetValue
>> _CFRelease
>> _CFStringGetCString
>> _IOIteratorNext
>> _IOMasterPort
>> _IOObjectRelease
>> _IORegistryEntryCreateCFProperty
>> _IOServiceGetMatchingServices
>> _IOServiceMatching
>> ___CFStringMakeConstantString
>> _kCFAllocatorDefault
>> _kCFBooleanTrue
>> make: *** [qemu-img] Error 1
>>
>> It seems to be unrelated to Fabrice's Cocoa changes and unrelated
>> to the AIO reversion. My guess is that the CoreFoundation framework
>> or something needs to be linked in. Any idea which commit might
>> have caused this or where to fix?
>
> Any hints, anyone? Still haven't figured out where this breakage is
> coming from, didn't notice any relevant changes in Makefile or
> configure...
>
> Andreas
>
Does it work if you specify "-framework CoreFoundation -framework
IOKit" in your LDFLAGS? That's what was needed on my Leopard x86_64
build.
Cheers,
Alex
next prev parent reply other threads:[~2007-12-12 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 12:40 [Qemu-devel] Mac OS X build failure (qemu-img) Andreas Färber
2007-12-12 11:39 ` Andreas Färber
2007-12-12 12:08 ` Alexander Graf [this message]
2007-12-13 23:19 ` Andreas Färber
2007-12-14 11:24 ` Alexander Graf
2007-12-14 15:17 ` Andreas Färber
2007-12-14 17:38 ` Alexander Graf
2008-01-07 23:20 ` [PATCH] " Andreas Färber
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=AE59A20B-5EBA-4F12-BFA7-4C3C7BA25E4C@csgraf.de \
--to=alex@csgraf.de \
--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).