From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Peter Dyballa 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: Tue, 19 Feb 2008 11:31:30 +0100 Message-ID: <94E6C176-81C7-481F-B24A-012FFEC24F8D@freenet.de> References: <200802181932.m1IJWiu7007097@sallyv1.ics.uci.edu> <200802190010.m1J0AVpZ018954@sallyv1.ics.uci.edu> <5EFB325D-55DD-40CA-B58C-B2B5EF2C3248@freenet.de> <200802190959.m1J9xJi4026244@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1203417299 9758 80.91.229.12 (19 Feb 2008 10:34:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 Feb 2008 10:34:59 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 19 11:35:22 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 1JRPol-00076d-NG for ged-emacs-devel@m.gmane.org; Tue, 19 Feb 2008 11:35:20 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JRPoG-0002cL-Mf for ged-emacs-devel@m.gmane.org; Tue, 19 Feb 2008 05:34:48 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JRPlH-0000WH-D8 for emacs-devel@gnu.org; Tue, 19 Feb 2008 05:31:43 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JRPlF-0000Te-EJ for emacs-devel@gnu.org; Tue, 19 Feb 2008 05:31:42 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JRPlE-0000Sy-7r for emacs-devel@gnu.org; Tue, 19 Feb 2008 05:31:40 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JRPlD-0006A8-WA for emacs-devel@gnu.org; Tue, 19 Feb 2008 05:31:40 -0500 Original-Received: from mx10.gnu.org ([199.232.76.166]) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JRPlD-00025q-Ns for emacs-pretest-bug@gnu.org; Tue, 19 Feb 2008 05:31:39 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JRPlA-00069G-KS for emacs-pretest-bug@gnu.org; Tue, 19 Feb 2008 05:31:39 -0500 Original-Received: from mout3.freenet.de ([195.4.92.93]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JRPlA-00068E-3Z for emacs-pretest-bug@gnu.org; Tue, 19 Feb 2008 05:31:36 -0500 Original-Received: from [195.4.92.22] (helo=12.mx.freenet.de) by mout3.freenet.de with esmtpa (Exim 4.69) (envelope-from ) id 1JRPl8-0005qb-7Q; Tue, 19 Feb 2008 11:31:34 +0100 Original-Received: from fccbb.f.ppp-pool.de ([195.4.204.187]:52813 helo=[192.168.1.2]) by 12.mx.freenet.de with esmtpsa (ID peter_dyballa@freenet.de) (TLSv1:AES128-SHA:128) (port 25) (Exim 4.69 #10) id 1JRPl7-0003ZI-Na; Tue, 19 Feb 2008 11:31:34 +0100 In-Reply-To: <200802190959.m1J9xJi4026244@sallyv1.ics.uci.edu> X-Mailer: Apple Mail (2.753) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:89563 gmane.emacs.pretest.bugs:21216 Archived-At: Am 19.02.2008 um 10:59 schrieb Dan Nicolaescu: >> >> I never had the idea of linking two libraries of the same kind (this >> sounds to me quite damaged). In the Mac OS X environment it happens > > Is this in the default Mac OS X environment, or this happens in your > particular setup? I'd say it's the standard behaviour. > >> that both shared libraries are presented to the application, as >> recorded in the Mac OS X crash dump. I want to avoid this situation >> by statically linking one of them to avoid that the application asks >> for one particular shared library =96 and gets two presented. And by > > As I said in the previous message, statically linking one version =20 > of the > library still means you are linking the same library twice. Could you explain this? I can't understand why I am linking a library =20= twice by linking it statically once ... > > The very complex configure flags that your have posted in a previous > message seem to indicate that something is seriously strange in your > setup. Yes: I have old and inadequate libraries that come with the OS and I =20 have newer more adequate ones. > > Does > ldd emacs > (or the equivalent of ldd on Mac OS X) > show the library twice? No. Otool -L reports it only once. Like this: /sw/lib/fontconfig2/lib/libfontconfig.1.dylib (compatibility = version =20 3.0.0, current version 3.0.0) /sw/lib/freetype219/lib/libfreetype.6.dylib (compatibility = version =20 10.0.0, current version 10.10.0) /sw/lib/libXaw3d.7.dylib (compatibility version 7.0.0, current =20= version 7.0.0) /sw/lib/libdbus-1.3.dylib (compatibility version 6.0.0, current =20= version 6.0.0) /sw/lib/libgdk_pixbuf-2.0.0.dylib (compatibility version = 601.0.0, =20 current version 601.10.0) /sw/lib/libgif.4.dylib (compatibility version 6.0.0, current = version =20 6.4.0) /sw/lib/libglib-2.0.0.dylib (compatibility version 1201.0.0, = current =20 version 1201.12.0) /sw/lib/libgmodule-2.0.0.dylib (compatibility version 1201.0.0, =20= current version 1201.12.0) /sw/lib/libgobject-2.0.0.dylib (compatibility version 1201.0.0, =20= current version 1201.12.0) /sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current =20= version 7.0.0) /sw/lib/libintl.3.dylib (compatibility version 8.0.0, current =20= version 8.3.0) /sw/lib/libjpeg.62.dylib (compatibility version 63.0.0, current =20= version 63.0.0) /sw/lib/libotf.0.dylib (compatibility version 1.0.0, current = version =20 1.0.0) /sw/lib/libpng12.0.dylib (compatibility version 19.0.0, current =20= version 19.0.0) /sw/lib/librsvg-2.2.dylib (compatibility version 12.0.0, current = =20 version 12.5.0) /sw/lib/libtiff.3.dylib (compatibility version 12.0.0, current =20= version 12.2.0) /sw/lib/ncurses/libncurses.5.dylib (compatibility version 5.0.0, = =20 current version 5.0.0) /usr/X11R6/lib/libICE.6.dylib (compatibility version 6.3.0, = current =20 version 6.3.0) /usr/X11R6/lib/libSM.6.dylib (compatibility version 6.0.0, = current =20 version 6.0.0) /usr/X11R6/lib/libX11.6.dylib (compatibility version 6.2.0, = current =20 version 6.2.0) /usr/X11R6/lib/libXext.6.dylib (compatibility version 6.4.0, = current =20 version 6.4.0) /usr/X11R6/lib/libXft.2.dylib (compatibility version 2.1.0, = current =20 version 2.1.0) /usr/X11R6/lib/libXmu.6.dylib (compatibility version 6.2.0, = current =20 version 6.2.0) /usr/X11R6/lib/libXpm.4.dylib (compatibility version 4.11.0, = current =20 version 4.11.0) /usr/X11R6/lib/libXt.6.dylib (compatibility version 6.0.0, = current =20 version 6.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current = =20 version 88.1.10) /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current = version =20 92.0.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current = version =20 1.2.3) > > >> choosing one library I might be able to find some details that might >> explain why GNU Emacs crashes. > > Linking 2 versions of the same library is extremely likely to cause =20= > very > strange crashed. Sorry, I don't have the idea of doing what you are suggesting. -- Greetings Pete These are my principles and if you don't like them... well, I have =20 others. - Groucho Marx