From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.60; How to make some libraries link statically via pkg-config files? Date: Mon, 18 Feb 2008 16:10:31 -0800 Message-ID: <200802190010.m1J0AVpZ018954@sallyv1.ics.uci.edu> References: <200802181932.m1IJWiu7007097@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1203380014 10777 80.91.229.12 (19 Feb 2008 00:13:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 Feb 2008 00:13:34 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org To: Peter Dyballa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 19 01:13:57 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JRG7P-0002hU-Dj for ged-emacs-devel@m.gmane.org; Tue, 19 Feb 2008 01:13:55 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JRG6u-0003Et-Jr for ged-emacs-devel@m.gmane.org; Mon, 18 Feb 2008 19:13:24 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JRG6q-0003Ds-FA for emacs-devel@gnu.org; Mon, 18 Feb 2008 19:13:20 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JRG6p-0003DW-O7 for emacs-devel@gnu.org; Mon, 18 Feb 2008 19:13:20 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JRG6p-0003DM-JN for emacs-devel@gnu.org; Mon, 18 Feb 2008 19:13:19 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JRG6p-00048Y-7V for emacs-devel@gnu.org; Mon, 18 Feb 2008 19:13:19 -0500 Original-Received: from mail.gnu.org ([199.232.76.166] helo=mx10.gnu.org) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JRG6o-0007G3-Uo for emacs-pretest-bug@gnu.org; Mon, 18 Feb 2008 19:13:19 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JRG6l-00047M-Gj for emacs-pretest-bug@gnu.org; Mon, 18 Feb 2008 19:13:18 -0500 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1JRG6l-00046O-3i for emacs-pretest-bug@gnu.org; Mon, 18 Feb 2008 19:13:15 -0500 X-ICS-MailScanner-Watermark: 1203984634.09538@uAJrid3aEub2VPnsJxk/SA Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m1J0AVpZ018954; Mon, 18 Feb 2008 16:10:31 -0800 (PST) In-Reply-To: (Peter Dyballa's message of "Tue, 19 Feb 2008 00:51:47 +0100") Original-Lines: 22 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:89536 gmane.emacs.pretest.bugs:21209 Archived-At: Peter Dyballa writes: > Am 18.02.2008 um 20:32 schrieb Dan Nicolaescu: > > > Your problem lies in linking 2 versions of the same library. You > > should > > only ever do that if you know exactly what you are doing, and know > > details about the libraries and their users. > > > > So, IMO, there's nothing that emacs should do about this. > > Yes. And therefore I want to delegate this to ld to link those > libraries that exist twice statically when I have control which > library gets used. Again, if you are trying to link the 2 versions of the same library twice you are asking for trouble. It can be made work if you know what your are doing, but it's not a good idea. If you do such a thing, and report bugs here, please explicitly say this in each bug report. IMHO it's better to figure out a way to avoid linking 2 versions of the same library than to play any tricks with the config files, linker, etc.