pcp
[Top] [All Lists]

Re: configure ignores --prefix argument

To: James Peach <jamespeach@xxxxxxx>
Subject: Re: configure ignores --prefix argument
From: Nathan Scott <nscott@xxxxxxxxxx>
Date: Tue, 25 Mar 2008 14:47:54 +1100
Cc: pcp@xxxxxxxxxxx
In-reply-to: <77AE5078-A6B3-47A0-B9F1-B1D68AF560E0@mac.com>
Organization: Aconex
References: <F9893D85-D2D5-4D9D-BBEF-12F6766A07AD@mac.com> <1206415921.29868.300.camel@edge.scott.net.au> <77AE5078-A6B3-47A0-B9F1-B1D68AF560E0@mac.com>
Reply-to: nscott@xxxxxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
On Mon, 2008-03-24 at 20:41 -0700, James Peach wrote:

> OK, I'll take a look at yr git tree and dig deeper if it's still not  
> working right.

Thanks.

> > for dir in /usr/bsd /usr/etc /usr/bin/X11 /usr/local/bin \
> >        /opt/sfw/bin /usr/ccs/bin /cygdrive/c/WINDOWS/system32 \
> > -       /usr/contrib/bin
> > +       /usr/contrib/bin /opt/local/bin
> 
> /opt/local/bin is installed by macports. I don't think it's a good  
> idea to have it in the standard PCP $PATH.
> 

I suspect that decision was made years ago, when /usr/local/bin
was put on the path - the intention there is fairly clear, even
if the original rationale is lost in the mists of time.

If configure is going off looking in these places for binaries,
then I guess we kinda have to have them on the path... (I don't
think hardcoded full-pathnames thing is gonna fly, as a general
solution to this class of problem).

cheers.

-- 
Nathan


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