Re: use of libtool for linking executables - rpath problem

2001-12-12 Thread Paul Eggert
From: Bruno Haible [EMAIL PROTECTED] Date: Tue, 11 Dec 2001 15:28:30 +0100 (CET) ftp://alpha.gnu.org/gnu/gettext/gettext-0.11-pre3.tar.gz. Thanks. I downloaded it and took a very brief look. It doesn't build on Solaris 8 + GCC 3.0.2 due to some really minor problems. If you've already

Re: use of libtool for linking executables - rpath problem

2001-12-11 Thread Bruno Haible
Paul Eggert writes: By the way, thanks for your analysis. This is a real problem that seems to me to be getting worse with time. The problem is now solved if you take the gettext.m4 and iconv.m4 autoconf macros from ftp://alpha.gnu.org/gnu/gettext/gettext-0.11-pre3.tar.gz. You also need to

Re: use of libtool for linking executables - rpath problem

2001-11-20 Thread Lars J. Aas
On Mon, Nov 19, 2001 at 11:36:21PM -0800, Russ Allbery wrote: : Bob Friesenhahn [EMAIL PROTECTED] writes: : How is the application developer to know which directories are searched : by default? : : One can safely assume that /usr/lib and /usr/include are always searched : by default. Those

Re: use of libtool for linking executables - rpath problem

2001-11-20 Thread Russ Allbery
Lars J Aas [EMAIL PROTECTED] writes: There are always exceptions. A bunch of projects I am a developer on uses the MS Visual C++ compiler when building on Cygwin platforms. Would you be surprised to know that VC++ does *not* search Cygwins /usr/include for headers by default? :) This sort

use of libtool for linking executables - rpath problem

2001-11-19 Thread Bruno Haible
Dear libtool gurus, More and more GNU packages start using shared libraries. One example is libintl (from the GNU gettext package), which installs itself as a shared library by default now. It is used by many other packages, like textutils, gcc, hello, and others, which don't use libtool. For

Re: use of libtool for linking executables - rpath problem

2001-11-19 Thread Paul Davis
I can see six possible approaches: The 7th is to have the shared library use pkg-config, allowing other tools to find out about it without relying on the linker configuration. Its much cleaner than any of the other choices you mention, and thankfully, has nothing to do with libtool (phew!) --p

Re: use of libtool for linking executables - rpath problem

2001-11-19 Thread Rob Browning
Bruno Haible [EMAIL PROTECTED] writes: 3) Introduce a libintl-config script that sets outputs the right -L and -rpath option. This may or may not help you if you're linking with *any* other tools that are installed in /usr/lib and their foo-config scripts output -L/usr/lib. In that case

Re: use of libtool for linking executables - rpath problem

2001-11-19 Thread Paul Jarc
Rob Browning [EMAIL PROTECTED] wrote: Bruno Haible [EMAIL PROTECTED] writes: 3) Introduce a libintl-config script that sets outputs the right -L and -rpath option. This may or may not help you if you're linking with *any* other tools that are installed in /usr/lib and their foo-config

Re: use of libtool for linking executables - rpath problem

2001-11-19 Thread Paul Eggert
From: Bruno Haible [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 19:08:59 +0100 (CET) 1) We don't change our packages. We only tell the user that he should have used LDFLAGS=-L${prefix}/lib -rpath ${prefix}/lib 6) Let each package search for 'libtool' in $PATH and use it if found,

Re: use of libtool for linking executables - rpath problem

2001-11-19 Thread Bruno Haible
Paul Eggert writes: 6) Let each package search for 'libtool' in $PATH and use it if found, and fall back to 1) if not found This works only when the same C compiler is used to build the package as was used to configure libtool. Can you please explain why (6) has this

Re: use of libtool for linking executables - rpath problem

2001-11-19 Thread Paul Davis
pkg-config doesn't do that. its an almost impossible task unless you Are you talking about some new tool that I had not previously heard about or are you talking about a script like the '/usr/local/bin/gnome-config' I see on my system? its a replacement for *all* such scripts. its a C

Re: use of libtool for linking executables - rpath problem

2001-11-19 Thread Russ Allbery
Rob Browning [EMAIL PROTECTED] writes: The problem I'm talking about is if Makefile.am's use LDFLAGS = `gnome-config --libs foo` `foo-config --libs bar` then if you've got a normal gnome-dev package installed, such that it's libs are in /usr/lib, it will (or at least it used to) put

Re: use of libtool for linking executables - rpath problem

2001-11-19 Thread Bob Friesenhahn
On 19 Nov 2001, Russ Allbery wrote: Rob Browning [EMAIL PROTECTED] writes: The problem I'm talking about is if Makefile.am's use LDFLAGS = `gnome-config --libs foo` `foo-config --libs bar` then if you've got a normal gnome-dev package installed, such that it's libs are in

Re: use of libtool for linking executables - rpath problem

2001-11-19 Thread Russ Allbery
Bob Friesenhahn [EMAIL PROTECTED] writes: How is the application developer to know which directories are searched by default? One can safely assume that /usr/lib and /usr/include are always searched by default. Those are the only ones that I'd expect people to automatically leave out of the