As long as the configm4's use PHP_ADD_LIBRARY_WITH_PATH()
and the other macros and don't touch LIBS themselves,
there won't be any /usr/lib entries in it
So, I'd check the la files There's propably libpspellla
which has -L/usr/lib defined in 'dependency_libs='
And then
On Sun, Mar 03, 2002 at 06:16:07PM +0200, Jani Taskinen wrote :
As long as the configm4's use PHP_ADD_LIBRARY_WITH_PATH()
and the other macros and don't touch LIBS themselves,
there won't be any /usr/lib entries in it
So, I'd check the la files There's propably
Libtool version? Not all have this problem
--Jani
On Sun, 3 Mar 2002, Markus Fischer wrote:
On Sun, Mar 03, 2002 at 06:16:07PM +0200, Jani Taskinen wrote :
As long as the configm4's use PHP_ADD_LIBRARY_WITH_PATH()
and the other macros and don't touch LIBS themselves,
On Sun, Mar 03, 2002 at 06:37:53PM +0200, Jani Taskinen wrote :
Libtool version? Not all have this problem
$ libtool --version
ltmainsh (GNU libtool) 14 (1920 2001/04/24 23:26:18)
I think I lost discussion point somewhere now sorry
--
Please always Cc to me when
Hmmit depends on so many things But the bug
exists only in some 14x versions (including 14)
--Jani
On Sun, 3 Mar 2002, Markus Fischer wrote:
On Sun, Mar 03, 2002 at 06:37:53PM +0200, Jani Taskinen wrote :
Libtool version? Not all have this problem
$ libtool --version
ltmainsh (GNU libtool) 14 (1920 2001/04/24 23:26:18)
And no, none of my /usr/lib/*pspell*la files have -L/usr/lib in their
dependency_libs Lots of other la files in /usr/lib have that, but not
pspell
-Rasmus
On Sun, 3 Mar 2002, Jani Taskinen wrote:
Libtool version? Not all have this
Ok, so the situation is this:
--with-gd=/some/dir
This will go through and do configure checks to figure out which version
of GD live in /some/dir Say a static libgda built from gd-201 is
sitting in there
If the system also has a /usr/lib/libgdso then as of 420 the -lgd is
picking up this
At 07:56 AM 3/2/2002 -0800, Rasmus Lerdorf wrote:
Ok, so the situation is this:
--with-gd=/some/dir
This will go through and do configure checks to figure out which version
of GD live in /some/dir Say a static libgda built from gd-201 is
sitting in there
If the system also has a
If the system also has a /usr/lib/libgdso then as of 420 the -lgd is
picking up this shared library
I suppose the only way around this is to use a full path to the static
library in the link line instead of -lgd Does a full path library link
work for a shared library as well? I didn't
At 08:03 AM 3/2/2002 -0800, Rasmus Lerdorf wrote:
If the system also has a /usr/lib/libgdso then as of 420 the -lgd is
picking up this shared library
I suppose the only way around this is to use a full path to the static
library in the link line instead of -lgd Does a full path
At 08:03 AM 3/2/2002 -0800, Rasmus Lerdorf wrote:
If the system also has a /usr/lib/libgdso then as of 420 the -lgd is
picking up this shared library
I suppose the only way around this is to use a full path to the static
library in the link line instead of -lgd Does a full path
On Sat, 2 Mar 2002, Rasmus Lerdorf wrote:
At 08:03 AM 3/2/2002 -0800, Rasmus Lerdorf wrote:
If the system also has a /usr/lib/libgdso then as of 420 the -lgd is
picking up this shared library
I suppose the only way around this is to use a full path to the static
library in the
The problem really is that when you give configure a path to some specific
place for a static library, but you also have that library as a shared
library in /usr/lib things get messy because we do the configure check
against the located static library explicitly, but then we do a
Hrm Ok, so the problem isn't as clearcut as I thought A walkthrough:
Install the gd-18x and gd-devel-18x packages on some common Linux
distro I am using an old rh-71 box with a bunch of upgraded packages
here Make sure it installs a /usr/lib/libgdso
Then download gd-201targz from boutellcom
On Sat, 2 Mar 2002, Rasmus Lerdorf wrote:
-L/usr/lib/gcc-lib/i386-redhat-linux/296///
-L/usr/lib/gcc-lib/i386-redhat-linux/296
-L/tmp/19246-i386/BUILD/pspell-122/modules/libs -L/usr/lib
This is the problem /usr/lib shouldn't be here
In your working build you won't see it
So, there
This is the problem /usr/lib shouldn't be here
In your working build you won't see it
Looks like ext/pspell/configm4 is the culprit
-Rasmus
--
PHP Development Mailing List http://wwwphpnet/
To unsubscribe, visit: http://wwwphpnet/unsubphp
16 matches
Mail list logo
