Re: Make error trying to install PEAR package manager
| From: | derek fong | Date: | Sun, 24 Mar 2002 23:12:08 +0000 |
| Subject: | Re: Make error trying to install PEAR package manager | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-1045@lists.php.net to get a copy of this message | ||
On 3.24.02 5:11 pm, "Stig S. Bakken" <ssb@fast.no> wrote:
> On Sun, 2002-03-24 at 09:06, derek fong wrote:
>>>> I must be missing something, but there's no configure script to be found in
>>>> php4... Should I have something else before doing the cvs checkout?
>>>
>>> The configure script is generated, and not kept in CVS. Run
>>> "./buildconf" to generated it. You will need autoconf, libtool and
>>> automake installed to do this.
>>
>> Hi Stig,
>>
>> Ok, I tried that and got a lot further now. Unfortunately, once the
>> configure script does its thing, I am now getting the following error trying
>> to do make install-data-local install-programs install-build:
>>
>> make: *** No rule to make target `install-data-local'. Stop.
>>
>> Yikes. What am I doing wrong now?
>
> "install-data-local" was just renamed to "install-pear", so try that
> instead.
Excellent! It all installs fine, but now I'm wondering exactly how to use
pear install. I used to have PEAR installed in /System/Library/PHP (under
Mac OS X), but I made a backup of it before I installed PEAR from CVS. I
notice there are lots of files that didn't make it from CVS into my new PEAR
directory, namely IT.php for templating. How exactly would one use the pear
command to install the IT package, for example? (A better question is where
do I get these packages, and what does a package look like?) Is there a way
I can get a list of all available packages? I notice there's a login
option, but I can't figure out how to create an account or why I would need
one.
-f
--
Derek Fong
Web Application Developer
subtitle designs inc. <http://www.subtitled.com/>
"Mistakes are the portals of discovery." --James Joyce
>> GPG key/fingerprint available upon request <<