On Oct 29, 2007, at 3:06 AM, Martin Costabel wrote:
Abe Stephens wrote:
Hi, I'm encountering a linking problem whenever I attempt to link
to X11's libGL in Leopard. Here is a concise example:
echo 'static void *foo; int main() { foo = (void
*)glGetIntegerv; }' | g++ -xc++ - -I/usr/X11R6/include -includeGL/
gl.h -L/usr/X11R6/lib -lGL
ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib
collect2: ld returned 1 exit status
Does anyone have some advice on how to fix this?
This is a new feature (AKA bug) in /usr/bin/ld, coupled with the
fact that Apple rather stupidly chose the same name "libGL.dylib"
for two linked but different libraries in /usr/X11/lib and in the
OpenGL framework.
No argument here that it's a bug, but there's a good reason that both
libraries have the same name -- both of them implement the same API,
one that is dictated by the OpenGL specification. A native Cocoa/
Carbon app might link against one of them, and a GLX app would link
against the other, but both of them would be making the same calls.
--
Ben Byer
CoreOS / BSD Technology Group, XDarwin maintainer
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/email@hidden
