From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22961 invoked by alias); 18 Dec 2008 06:01:24 -0000 Received: (qmail 22755 invoked by uid 22791); 18 Dec 2008 06:01:23 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from rn-out-0910.google.com (HELO rn-out-0910.google.com) (64.233.170.187) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Dec 2008 06:00:33 +0000 Received: by rn-out-0910.google.com with SMTP id k56so218960rnd.19 for ; Wed, 17 Dec 2008 22:00:30 -0800 (PST) Received: by 10.64.180.15 with SMTP id c15mr1250664qbf.80.1229580030558; Wed, 17 Dec 2008 22:00:30 -0800 (PST) Received: from ?192.168.0.100? (S0106001346f94b85.wp.shawcable.net [24.76.249.6]) by mx.google.com with ESMTPS id 9sm2701253qbw.21.2008.12.17.22.00.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 17 Dec 2008 22:00:29 -0800 (PST) Message-ID: <4949E6FD.6050508@users.sourceforge.net> Date: Thu, 18 Dec 2008 06:01:00 -0000 From: "Yaakov (Cygwin/X)" User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: GTK+ externals are unresolved References: <002701c95f06$c7c2e190$4001a8c0@mycomputer> <49480D5D.8090002@x-ray.at> <4948117F.6080208@users.sourceforge.net> <49495236.6080407@x-ray.at> <49497EE9.70504@users.sourceforge.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2008-12/txt/msg00438.txt.bz2 -----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/