Not if you only have 64bit libs installed, which is dangerous, since
otherwise it doesn't give any warnings and you're not getting what you
think you are.
You did have some -L/usr/lib 's sneak in from somewhere in the make
output you posted. Can you also upload the config.log produced?
On Mon, Feb 14, 2005 at 01:28:26PM -0500, Hans Zaunere wrote:
Not if you only have 64bit libs installed, which is dangerous, since
otherwise it doesn't give any warnings and you're not getting what you
think you are.
You did have some -L/usr/lib 's sneak in from somewhere in the make
output
I am still quite skeptical of this bundled libtool idea. It is
currently broken even on mainstream systems such as Debian x86 where
do to the crappy packaging it is really important that people can
build their own. See http://lerdorf.com/php/libtool.txt for a
./buildconf
Lester Caine wrote:
Rasmus Lerdorf wrote:
I am still quite skeptical of this bundled libtool idea. It is
currently broken even on mainstream systems such as Debian x86 where
do to the crappy packaging it is really important that people can
build their own. See
Rasmus Lerdorf wrote:
Works ok as far as I know. The above-mentioned problem turned out to be
an incompatibility between my own ltmain.sh I was using and the
m4-generated libtool. With a completely clean tree it does work.
Ta. When I find a few extra hours ... ;)
--
Lester Caine
Rasmus Lerdorf wrote:
I am still quite skeptical of this bundled libtool idea. It is
currently broken even on mainstream systems such as Debian x86 where do
to the crappy packaging it is really important that people can build
their own. See http://lerdorf.com/php/libtool.txt for a ./buildconf
On Mon, 7 Feb 2005, Hans Zaunere wrote:
My system build environment (Fedora Core 2, updated) has the following:
ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.95 2004/04/11 05:50:42)
autoconf (GNU Autoconf) 2.59
automake (GNU automake) 1.8.3
This had worked a few months ago, when we first started on this
My system build environment (Fedora Core 2, updated) has the following:
ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.95 2004/04/11 05:50:42)
autoconf (GNU Autoconf) 2.59
automake (GNU automake) 1.8.3
This had worked a few months ago, when we first started on this stuff.
So it seems
Jani Taskinen wrote:
On Mon, 7 Feb 2005, Hans Zaunere wrote:
My system build environment (Fedora Core 2, updated) has the following:
ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.95 2004/04/11 05:50:42)
autoconf (GNU Autoconf) 2.59
automake (GNU automake) 1.8.3
This had worked a few months ago, when we
On Sat, Feb 05, 2005 at 07:03:52PM -0500, Hans Zaunere wrote:
...
However, after downloading the php5-200502052330.tar.gz snapshot,
things seem broken again. My ./configure starts out like this:
./configure --with-libdir=lib64 --prefix=/usr/local/php
--with-apxs=/usr/local/apache/bin/apxs
However, after downloading the php5-200502052330.tar.gz snapshot,
things seem broken again. My ./configure starts out like this:
./configure --with-libdir=lib64 --prefix=/usr/local/php --with-
apxs=/usr/local/apache/bin/apxs
.
Which had worked fine before. However, when
On Mon, Feb 07, 2005 at 10:09:29AM -0500, Hans Zaunere wrote:
However, after downloading the php5-200502052330.tar.gz snapshot,
things seem broken again. My ./configure starts out like this:
./configure --with-libdir=lib64 --prefix=/usr/local/php --with-
However, after downloading the php5-200502052330.tar.gz snapshot,
things seem broken again. My ./configure starts out like this:
./configure --with-libdir=lib64 --prefix=/usr/local/php --with-
apxs=/usr/local/apache/bin/apxs
.
Which had worked fine before.
Some time ago we talked about compiling PHP on an AMD64. Joe Orton was kind
enough to patch the 5.1 branch to include the --with-libdir directive to
./configure to allow for searching in libs in such places as /lib64 and
/usr/lib64 and it worked great.
However, after downloading the
14 matches
Mail list logo
