Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:22771
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <47606.67.184.121.112.1145051796.squirrel@www.l-i-e.com>
In-Reply-To: <915441436.20060414130513@marcus-boerger.de>
References: <47455.67.184.121.112.1145010952.squirrel@www.l-i-e.com>
	<915441436.20060414130513@marcus-boerger.de>
Date: Fri, 14 Apr 2006 16:56:36 -0500 (CDT)
To: "Marcus Boerger" <helly@php.net>
Cc: internals@lists.php.net
Reply-To: ceo@l-i-e.com
User-Agent: Hostbaby Webmail
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] Re: ICU? step forward, two steps back
From: ceo@l-i-e.com ("Richard Lynch")

On Fri, April 14, 2006 6:05 am, Marcus Boerger wrote:
>   you forgot the include path...did you ever compile anything?

I compile PHP from source routinely.

I install a bunch of stuff from source all the time.

Though, admittedly, usually on my own box, where I don't have to deal
with trying to "split" the inter-dependent libraries between two
different directory paths.

I did not "forget" the include path.

Thought, perhaps, my reading of ./configure --help is incorrect...

The implication from that output, to me, is that if I set --prefix,
then the include path and lib path will be set to PREFIX/include and
PREFIX/lib

Those are, I think, what I want.

I have also attempted to manually set the includedir and libdir to:
~/cvs/usr/local/include
~/cvs/usr/local/lib
(only I typed the full path, of course, not relying on shell expansion)

That, however, caused problems when configure went looking for other
required libraries which are in the usual place in /usr/local/lib

So then I tried includedir and libdir:
~/cvs/usr/local/include:/usr/local/include
~/cvs/usr/local/lib:/usr/local/lib

I thought that that would get everything to check my home dirs first,
then the "usual" dirs second, to find whatever it needed.

I'll try that again, as it seems the most reasonable -- It's possible
I just made a typo in that one, as I was so tired.

The thing is, virtually all the "How-Tos" I can find only cover the
"normal" situation of compiling software to install in your base
installation "for real" instead of compiling, as I am, for development
situation.

And they also all gloss over what these configure args actually mean
and how they interact.  I'm the kind of guy that needs a longer
explanation of what these things DO in order to understand how to use
them, and I've failed to find that. [shrug]

Maybe if I ever really figure it out, I'll type it up somewhere.

Usually, though, after I get it to work, I don't really understand why
the thing I did worked, and the other things I did didn't work, so
it's more Voodoo than anything.  Not much point in trying to document
Voodoo Programming, eh?

-- 
Like Music?
http://l-i-e.com/artists.htm