Charles Celerier writes:
> I will be the first too admit that I do not know much about configure
> scripts, but adding a TRUE variable seemed straightforward.
configure is already big enough, I'd prefer not to add new things unless
they are needed. This is not likely to be something the user
Charles Celerier writes:
> The path to true may not be the same on all platforms (e.g. on Mac OS X
> it is /usr/bin/true), so the hard-coded path of /bin/true is not
> portable. This is resolved by adding a step to the configure script to
> locate the path of true and to use the TRUE variable
David Bremner writes:
> Charles Celerier writes:
>
>> The path to true may not be the same on all platforms (e.g. on Mac OS X
>> it is /usr/bin/true), so the hard-coded path of /bin/true is not
>> portable. This is resolved by adding a step to the configure script to
>> locate the path of true
Charles Celerier ccel...@cs.stanford.edu writes:
The path to true may not be the same on all platforms (e.g. on Mac OS X
it is /usr/bin/true), so the hard-coded path of /bin/true is not
portable. This is resolved by adding a step to the configure script to
locate the path of true and to use
David Bremner da...@tethera.net writes:
Charles Celerier ccel...@cs.stanford.edu writes:
The path to true may not be the same on all platforms (e.g. on Mac OS X
it is /usr/bin/true), so the hard-coded path of /bin/true is not
portable. This is resolved by adding a step to the configure
Charles Celerier ccel...@cs.stanford.edu writes:
I will be the first too admit that I do not know much about configure
scripts, but adding a TRUE variable seemed straightforward.
configure is already big enough, I'd prefer not to add new things unless
they are needed. This is not likely to
The path to true may not be the same on all platforms (e.g. on Mac OS X
it is /usr/bin/true), so the hard-coded path of /bin/true is not
portable. This is resolved by adding a step to the configure script to
locate the path of true and to use the TRUE variable wherever /bin/true
was needed. The
