Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:13332
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 14 Oct 2004 08:22:08 +0200 (CEST)
To: Hans Zaunere <hans@nyphp.com>
cc: internals@lists.php.net
In-Reply-To: <41EE526EC2D3C74286415780D3BA9F8704F13AAA@ehost011-1.exch011.intermedia.net>
Message-ID: <Pine.LNX.4.58.0410140813110.1897@localhost>
References: <41EE526EC2D3C74286415780D3BA9F8704F13AAA@ehost011-1.exch011.intermedia.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: RE: [PHP-DEV] ./configure, PHP, SuSE and the AMD64
From: derick@php.net (Derick Rethans)

On Wed, 13 Oct 2004, Hans Zaunere wrote:

> > > As I mentioned in my original post, --with-module and
> > > --with-module-dir seem to have some inconsistencies themselves as
> > > well.  What is the behavior?
> >
> > Where are the inconsistencies, can you point those out?
>
> Here are some notes additions from my previous post.
>
> In fact, there appear to be some inconstancies, and certainly some
> questions:
>
> > --with-openssl  (must not have any directory after it,
> > which isn't inline with what ./configure --help says).
>
> This just seems right-out broken...

OpenSSL is a special beast, though I can't see so quickly where the
message is generated.

> > --with-zlib=/usr  (this works - but what if I want to
> > force the 64bit library version, in /usr/lib64?)
>
> This is seems to be related to this thread, specifically lib64.

Yes, so it's not an inconsistency ;-)

> > --with-bz2=/usr/lib64  (and this also works - which you
> > would think it shouldn't, compared to the zlib above?)
>
> Just confusion... perhaps on my part, or inconsistencies in the way
> ./configure works.

If it works it is because we fall back to the default dir after this, so
it would fallback to /usr/lib and /usr/include.

>
> > And lastly, take these:
> >
> > --with-curl=/usr/lib64

See above.

> > --with-zlib-dir=/usr/lib64
> >
> > Both seem to work (so far).  So what is the difference
> > between a directive having the -dir suffix and not?
>
> Compare --with-zlib and --with-zlib-dir, per above.  Things sometimes
> "work" (meaning there are no obvious errors) and sometimes not; so how
> should the two be used?  What does the suffix -dir mean and how should
> it be used?

zlib-dir is odd indeed, it will override the dir from --with-zlib. No
clue why :)

> Agreed. ./configure should 1) have defaults of lib's locations  2) use
> system linker variables  and most importantly  3) allow specific
> directories to be specified during ./configure time.

1, sure, we do that. Not sure what you mean by 2) and 3) i don't agree
with as it is common to specify the install root dir which we've been
doing for ages.

>
> > shot, but I'll need to have access to a linux running on 64bit first
> :)
>
> That's not a problem, see follow-up message.

It wasn't a problem, more people already offered an account while you
were sleeping ;-)

Derick

-- 
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org