I have gotten it to compile pretty close to the end. It now fails at:
gcc -Wall -Wformat -Wmissing-prototypes -Wnested-externs -Wpointer-
arith -Wextra -Wshadow -Wcast-align -Wwrite-strings -Waggregate-return
-Wstrict-prototypes -Winline -Wredundant-decls -Wno-sign-compare -Wp,-
D_FORTIFY_SOURCE=2 -fexceptions -fasynchronous-unwind-tables -g -O2 -
o .libs/event-test event_test-event-test.o -L/opt/local/lib ../../../
src/.libs/libvirt.dylib -L/usr/lib /usr/lib/libxml2.dylib -licucore -
lm /opt/local/lib/libgnutls.dylib /opt/local/lib/libtasn1.dylib -lz /
opt/local/lib/libgcrypt.dylib /opt/local/lib/libgpg-error.dylib -
lpthread /opt/local/lib/libintl.dylib /opt/local/lib/libiconv.dylib -lc
Undefined symbols:
"_rpl_poll$UNIX2003", referenced from:
_main in event_test-event-test.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [event-test] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
The UNIX2003 symbol does not exist in 10.4, only in 10.5. I compiled
libvirt's dependencies under 10.5, and I am compiling libvirt under
10.5, so I do not know why one of its dependencies is clearly compiled
by linking to pre-10.5. The question I have is this. Where can I
comment out the necessity for this symbol, and will doing so kill the
libvirt remote client?
--
-a
"Ideally, a code library must be immediately usable by naive
developers, easily customized by more sophisticated developers, and
readily extensible by experts." -- L. Stein
On May 7, 2009, at 4:44 AM, Daniel Veillard wrote:
On Thu, May 07, 2009 at 11:38:26AM +0200, Pritesh Kothari wrote:
> On Thursday 07 May 2009 11:20:10 Daniel Veillard wrote:
>> On Wed, May 06, 2009 at 03:20:23PM -0500, Schley Andrew Kutz wrote:
>>> Anyone? :( I really don't want to have to bring up a whole new
>>> box just
>>> do do dev work that I should be able to do from my Mac. I guess I
>>> can
>>> write against the Java bindings locally and then debug remotely
>>> on a
>>> Linux server.
>>
>> Well, not that many people seems interested in porting to OS-X,
>> partly I guess because there is no support there for KVM or Xen.
>> I don't know what hypervisor could be used there, but for remote
>
> VirtualBox supports Mac OS X/Solaris/Windows/etc.. so i would
> try to do this, but in spare time as that is not on my todo list as
> of now.
Ah, cool, thanks !
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit
http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine
http://rpmfind.net/
http://veillard.com/ | virtualization library
http://libvirt.org/