pcp
[Top] [All Lists]

Re: pcp updates

To: Max Matveev <makc@xxxxxxx>
Subject: Re: pcp updates
From: Nathan Scott <nscott@xxxxxxxxxx>
Date: Wed, 26 Mar 2008 11:06:27 +1100
Cc: pcp@xxxxxxxxxxx
In-reply-to: <18409.37370.928974.771025@xxxxxxxxxxxxxxxxxxxxxx>
Organization: Aconex
References: <1206487246.29868.357.camel@xxxxxxxxxxxxxxxxx> <18409.36113.282730.586306@xxxxxxxxxxxxxxxxxxxxxx> <1206488515.29868.360.camel@xxxxxxxxxxxxxxxxx> <18409.37370.928974.771025@xxxxxxxxxxxxxxxxxxxxxx>
Reply-to: nscott@xxxxxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
On Wed, 2008-03-26 at 10:59 +1100, Max Matveev wrote:
> 
>  nscott> Most users expect to be able to do what James did - type:
>  nscott> ./configure --prefix=xxx && make
> 
>  nscott> That basic function does not work in the PCP build atm,
>  nscott> and the only sensible way I see to fix it, while keeping
>  nscott> the automatic ./configure via make, is the above change.
> But it's the wrong change because it creates extra crap which is not
> needed except as a crutch to crippled make.

By "wrong" you mean "suboptimal" or "not ideal"?
It works just fine, so its hard to see how its wrong.

> 
> If you really want to be able to make configure independed (which I

Its optionally independent, which is different.

> think is dangerous) then pick a real file it creates and change

Why is it dangerous?  Is it less dangerous than installing
to /usr when user requests /usr/local?

> Makefile rules to depend on this file instead of config.done.

Yeah, thats another option.  I guess any of the AC_OUTPUT
files (or all?) would do.

cheers.

-- 
Nathan


<Prev in Thread] Current Thread [Next in Thread>