Bug 14638 - Undefined symbols when creating .libs/libglib.so on Mac OS X
Summary: Undefined symbols when creating .libs/libglib.so on Mac OS X
Alias: None
Product: xorg
Classification: Unclassified
Component: App/compiz (show other bugs)
Version: 7.1 (2006.05)
Hardware: PowerPC Mac OS X (All)
: medium normal
Assignee: David Reveman
QA Contact: Xorg Project Team
Depends on:
Reported: 2008-02-23 12:46 UTC by Peter Dyballa
Modified: 2009-02-07 02:21 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Peter Dyballa 2008-02-23 12:46:36 UTC
Making all in plugins
	/bin/sh ../libtool --tag=CC --mode=link gcc  -v -pipe -fPIC -O0 -mcpu=7450 -mtune=7450 -fno-common -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -D_FORTIFY_SOURCE=2  -dead_strip -bind_at_load -L/sw/lib/freetype219/lib -L/sw/lib/fontconfig2/lib -L/sw/lib/ncurses -L/sw/lib -L/usr/local/lib -o libglib.la -rpath /usr/X11R7.1/lib/compiz -module -avoid-version -no-undefined glib.lo -L/sw/lib -lglib-2.0 -lintl -liconv   
	gcc  -o .libs/libglib.so -bundle  .libs/glib.o  -L/sw/lib/freetype219/lib -L/sw/lib/fontconfig2/lib -L/sw/lib/ncurses -L/sw/lib -L/usr/local/lib /sw/lib/libglib-2.0.dylib /sw/lib/libintl.dylib /sw/lib/libiconv.dylib -mcpu=7450 -mtune=7450
	/usr/bin/ld: warning -prebind has no effect with -bundle
	/usr/bin/ld: Undefined symbols:
	collect2: ld returned 1 exit status
	make[2]: *** [libglib.la] Error 1
	make[1]: *** [all-recursive] Error 1
	make: *** [all] Error 2

The library to be created should have the extension dylib instead of so, and libtool should not use -bundle – this switch is better used for a real Mac OS X application bundle. I think all Mac OS X support is missing here ...
Comment 1 Kristian Lyngstøl 2009-02-07 02:21:49 UTC
We currently do not support Mac OS X. If you wish to develop this idea, bring it up at the development mailing list.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.