From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: kai.grossjohann@gmx.net (=?iso-8859-1?q?Kai_Gro=DFjohann?=) Newsgroups: gmane.emacs.help Subject: Re: emacs 21.3 wants "libXaw3d.so.5"; got Xaw3d-1.5.tar.gz; NOW WHAT? Date: Mon, 26 May 2003 08:57:35 +0200 Organization: University of Duisburg, Germany Sender: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <84r86myz34.fsf@lucy.is.informatik.uni-duisburg.de> References: <84he7nutvd.fsf@lucy.is.informatik.uni-duisburg.de> <84of1uxhwp.fsf@lucy.is.informatik.uni-duisburg.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1053932460 16290 80.91.224.249 (26 May 2003 07:01:00 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 26 May 2003 07:01:00 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Mon May 26 09:00:57 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19KByb-0004ET-00 for ; Mon, 26 May 2003 09:00:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19KBz5-0003Hd-E7 for gnu-help-gnu-emacs@m.gmane.org; Mon, 26 May 2003 03:01:27 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!nntp.cs.ubc.ca!fu-berlin.de!uni-berlin.de!lucy.is.informatik.uni-duisburg.DE!not-for-mail Original-Newsgroups: gnu.emacs.help,comp.unix.solaris Original-Lines: 59 Original-NNTP-Posting-Host: lucy.is.informatik.uni-duisburg.de (134.91.35.216) Original-X-Trace: fu-berlin.de 1053932276 2927285 134.91.35.216 (16 [73968]) Mail-Copies-To: never User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:C401OcysTKcZGFKs25mTVYuntmg= Original-Xref: shelby.stanford.edu gnu.emacs.help:113686 comp.unix.solaris:443267 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:10181 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:10181 dkcombs@panix.com (David Combs) writes: > Now, on that other thread, there has been SO MUCH back- and-forth > about the args, one saying "add this -R xxx" and the followup saying > eg ~~ "no, no, no -- don't do that! It won't work!" -- please, for > me, and for the eventual writeup that I promised: > > (1) exactly what arg for the -L? (and why) The argument for -L should be where the library lives. So if you want to include the library /opt/some_package/lib/libfoo.so, then you should add -L/opt/some_package/lib. -L tells the linker to look in that directory when constructing the executable. > (2) ditto for the -R. The argument for -R should be the same as for -L. -R tells the executable where to find its libraries when running. When -R is not specfied, the executable (the loader, actually) will look in the directories listed in $LD_LIBRARY_PATH. I'm not sure whether the linker will also look there or only in -L. > (3) Something to pre-answer a "no no no!" kind of followup. The obvious alternative, to me, would be to specify the directory via $LD_LIBRARY_PATH when the executable is run. So what you could do is to use -L to specify a directory for the linker, and then each user can use $LD_LIBRARY_PATH to choose the directory when running. This way, you could specify -L/foo/1.4/lib but later on, when a new version of foo is released, you could change $LD_LIBRARY_PATH from /foo/1.4/lib to /foo/1.5/lib and then the executable would use the new library. > (4) (I assume there's more than one way to successfully > build this new Emacs -- or is there essentially only > ONE way?) There are advantages for the -R solution (always finds the library that Emacs was built with) and also for the $LD_LIBRARY_PATH solution (can use bugfixed library without recompiling Emacs). My personal opinion is that it is safer to use -R because strange problems may arise when run Emacs with a different library (version) than it was built with. If the bugfix from the new library version is really needed, it is easy enough to build Emacs again. > (5) What is it that makes this 21.3 (or just 21.x?) > more difficult, more understanding needed, than > 20.x, 19.x? Emacs 21 uses more external libraries, for displaying images for instance. -- This line is not blank.