httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <ab...@dial.pipex.com>
Subject Re: Buildconf...
Date Sun, 06 Feb 2000 19:46:52 GMT
Well then why in the hell did we write this to use which?
Groan...why do we keep going back over the same problems?

d.
----- Original Message -----
From: "Ralf S. Engelschall" <rse@engelschall.com>
To: <new-httpd@apache.org>
Sent: Sunday, February 06, 2000 6:50 PM
Subject: Re: Buildconf...


>
> In article <007801bf70b9$bf4da260$0a1aa8c0@jetnet.co.uk> you wrote:
>
> > Jeff replied to the problem I had with a solution which I'm happy to
report
> > works.
> > Question is how to correct it?
> >
> > BeOS doesn't have "which" but does support "type -path".  Can we change
the
> > line
> >
> > @n=`which libtool`; echo libtool_prefix = `dirname $$n`/.. >> $@
> >
> > to
> >
> > @n=`/bin/sh -c "type -path libtool"`; echo libtool_prefix = `dirname
$$n`/..
> >>> $@
> >
> > in src/build/build.mk or will that break other platforms?  If BeOS is
the
> > only one affected then I can create a small shell script called which to
do
> > the job.
>
> There actually is such a shell script: PrintPath
> Because the only portable way is to iterate over $PATH manually.
> Both "type" and "which" are usually not portable enough...
>
>                                        Ralf S. Engelschall
>                                        rse@engelschall.com
>                                        www.engelschall.com


Mime
View raw message