GTK+ externals are unresolved

Reini Urban rurban@x-ray.at
Sat Dec 20 15:44:00 GMT 2008


Yaakov (Cygwin/X) schrieb:
> René Berber wrote:
>> You're wrong, libraries shared or static are dealt the same way by the
>> compiler which looks for its list of unresolved symbols and doesn't
>> re-scan libraries when another symbol appears.
> 
> Since I apparently didn't make myself clear the last two times, let me
> say it again.  If libfoo is a shared library, and libbar is another
> shared library that depends on libfoo (and on Cygwin is, by definition,
> already linked against it), it does NOT matter if you do this:
> 
> gcc -o baz.exe baz.o -lbar -lfoo
> 
> or this:
> 
> gcc -o baz.exe baz.o -lfoo -lbar
> 
> Now if we link with -static, then of course it needs to be before -lfoo,
> just like baz.o which depends on libbar needs to be before -lbar.
> 
> But that's not the case here; all the GNOME libraries are shared, and
> pkg-config's order is ultimately correct.
> 
> Bottom line: this linking order discussion is a red herring.  My
> suspicion is that there is a mixing of the versions provided by the
> distro and Ports.

Anyway, it compiles with my fixed order and gives the unresolved symbols 
with the original $(pkg-config --libs gtk+-2.0) order of libs.
Please try it our yourself.
-- 
Reini Urban

-------------- next part --------------
An embedded message was scrubbed...
From: Reini Urban <rurban@x-ray.at>
Subject: Re: GTK+ externals are unresolved
Date: Tue, 16 Dec 2008 21:19:41 +0100
Size: 4669
URL: <http://cygwin.com/pipermail/cygwin/attachments/20081220/038ac14c/attachment.eml>
-------------- next part --------------
--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


More information about the Cygwin mailing list