Re: Question about relink_command

2010-05-31 Thread Alex Farber
Thank you for information. Alex On Mon, May 31, 2010 at 10:15 PM, Ralf Wildenhues wrote: > Hello, > > * Gary V. Vaughan wrote on Mon, May 31, 2010 at 05:53:26PM CEST: > > AFAIK Linux binaries/libraries can be built in the build tree with > > no hardcoded references to other objects in the build

Re: Question about relink_command

2010-05-31 Thread Ralf Wildenhues
Hello, * Gary V. Vaughan wrote on Mon, May 31, 2010 at 05:53:26PM CEST: > AFAIK Linux binaries/libraries can be built in the build tree with > no hardcoded references to other objects in the build tree, so they > can always be copied into the install tree and continue working > (although libtool h

Re: Question about relink_command

2010-05-31 Thread Gary V. Vaughan
On May 31, 2010, at 5:11 PM, Alex Farber wrote: Sorry, I didn't understand the question. I just tried installation without relink_command, by removing relink_command from .la file, and it works. So, I wanted to know when it is really necessary. On Mon, May 31, 2010 at 10:29 AM

Re: Question about relink_command

2010-05-31 Thread Alex Farber
Sorry, I didn't understand the question. I just tried installation without relink_command, by removing relink_command from .la file, and it works. So, I wanted to know when it is really necessary. On Mon, May 31, 2010 at 10:29 AM, Tor Lillqvist wrote: > What makes you think the issue r

Re: Question about relink_command

2010-05-31 Thread Tor Lillqvist
What makes you think the issue relinking is related to would have anything to do with Linux in particular? --tml ___ http://lists.gnu.org/mailman/listinfo/libtool

Question about relink_command

2010-05-31 Thread Alex Farber
*.la file produced by libtool contains relink_command, which allows to relink this library during installation. According to libtool documentation, this is necessary on the systems where the linker always hardcodes paths to dependent libraries into the output. What Linux versions require this? I

Re: relink_command quoting bug

2004-02-18 Thread Bob Friesenhahn
On Wed, 18 Feb 2004, Scott James Remnant wrote: > > > We already did that some time ago, if you search -patches passim. you'll > find I did that and found an even bigger problem... > > When directory names contain spaces the following kinda breaks... > > deplibs="-L/path/to/directory with/spaces in

Re: relink_command quoting bug

2004-02-18 Thread Scott James Remnant
On Tue, 2004-02-17 at 13:27, Peter O'Gorman wrote: > Michael Pruett wrote: > | The change you suggested fixed the first problem but not the second. > > We probably need to go through ltmain.in and modify every line containing > pwd we find, then modify every line that uses the vars that were assi

Re: relink_command quoting bug

2004-02-17 Thread Peter O'Gorman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Pruett wrote: | The change you suggested fixed the first problem but not the second. We probably need to go through ltmain.in and modify every line containing pwd we find, then modify every line that uses the vars that were assigned to the value

Re: relink_command quoting bug

2004-02-17 Thread Michael Pruett
On Tue, Feb 17, 2004 at 02:44:12AM -0600, Albert Chin wrote: > Search your "libtool" script for a line like: > relink_command="(cd `pwd`; ... > and change it to: > relink_command="(cd \"`pwd`\"; ... > > Does that fix it? I should have po

Re: relink_command quoting bug

2004-02-17 Thread Albert Chin
On Mon, Feb 16, 2004 at 11:39:17PM -0500, Michael Pruett wrote: > I have found that libtool fails to quote directory names when generating > relink_command in wrapper scripts. This has been tested with versions > 1.4.2a on Linux and 1.5.2 on Mac OS X. > > The wrapper scripts

relink_command quoting bug

2004-02-16 Thread Michael Pruett
I have found that libtool fails to quote directory names when generating relink_command in wrapper scripts. This has been tested with versions 1.4.2a on Linux and 1.5.2 on Mac OS X. The wrapper scripts generate a line which looks like the following: relink_command="(cd /home/michael/my cod

Re: relink_command

2000-07-26 Thread Alexandre Oliva
On Jul 24, 2000, Patrick Welche <[EMAIL PROTECTED]> wrote: > ltmain.sh generates wrapper scripts with a relink_command defined. In my > case, said command correctly has -L/usr/local/lib -L/usr/X11R6/lib, but only > has -Wl,--rpath -Wl,/usr/local/lib, no X11R6. What is the libto

Re: relink_command

2000-07-24 Thread Nick Hudson
Patrick Welche wrote: > > ltmain.sh generates wrapper scripts with a relink_command defined. In my > case, said command correctly has -L/usr/local/lib -L/usr/X11R6/lib, but only > has -Wl,--rpath -Wl,/usr/local/lib, no X11R6. I was hoping that both the -L > part and the --rpath

relink_command

2000-07-24 Thread Patrick Welche
ltmain.sh generates wrapper scripts with a relink_command defined. In my case, said command correctly has -L/usr/local/lib -L/usr/X11R6/lib, but only has -Wl,--rpath -Wl,/usr/local/lib, no X11R6. I was hoping that both the -L part and the --rpath part would grab $deplibs ? but they are obviously