Re: GTK+ externals are unresolved

["Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAklJ5v0ACgkQpiWmPGlmQSOK5ACfQch13kybWhj85NvVhyBNuBOZ
WmAAn0f3FHHMdB/OM2G9FUix46h1N7Hp
=kCJa
-----END PGP SIGNATURE-----

--
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/