www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <4949E6FD.6050508@users.sourceforge.net> |
Date: | Thu, 18 Dec 2008 00:00:29 -0600 |
From: | "Yaakov (Cygwin/X)" <yselkowitz AT users DOT sourceforge DOT net> |
User-Agent: | Thunderbird 2.0.0.18 (Windows/20081105) |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: GTK+ externals are unresolved |
References: | <loom DOT 20081215T211641-645 AT post DOT gmane DOT org> <002701c95f06$c7c2e190$4001a8c0 AT mycomputer> <loom DOT 20081216T190513-304 AT post DOT gmane DOT org> <49480D5D DOT 8090002 AT x-ray DOT at> <4948117F DOT 6080208 AT users DOT sourceforge DOT net> <49495236 DOT 6080407 AT x-ray DOT at> <49497EE9 DOT 70504 AT users DOT sourceforge DOT net> <gic6i4$lju$1 AT ger DOT gmane DOT org> |
In-Reply-To: | <gic6i4$lju$1@ger.gmane.org> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
-----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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |