Hrm... Removing this does produce an amazingly ugly link line. After playing a bit and getting frustrated that pre-setting LDFLAGS and even PHP_LDFLAGS in my env resulted in /usr/lib getting stripped out of those again I figured out that setting EXTRA_LDFLAGS to -L/usr/lib in my env lets me compile. That should do it for now I guess, but I can see others perhaps getting confused by this.
-Rasmus On Mon, 7 Oct 2002, Rasmus Lerdorf wrote: > The PHP_ADD_LIBPATH configure macro starts like this: > > AC_DEFUN(PHP_ADD_LIBPATH,[ > if test "$1" != "/usr/lib"; then > > And we also have a PHP_REMOVE_USR_LIB macro which is called on the > generated LDPATH string, so even if I do manage to sneak in my /usr/lib > directory somewhere it is removed. > > This is causing me problems in an environment where /usr/lib is not the > default primary link directory and I need to explicitly add it to get > stuff to compile right. Why is this check here? Just to pretty up the > link line? Would it hurt to leave this check off so /usr/lib can be > forced on weird systems? > > -Rasmus > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
