This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: rfc: new libgcc build mechanism
- To: Donn Terry <donnte at microsoft dot com>
- Subject: Re: rfc: new libgcc build mechanism
- From: Bruce Korb <bkorb at sco dot COM>
- Date: Tue, 09 May 2000 10:54:21 -0700
- CC: 'Robert Lipe' <robertlipe at usa dot net>, 'Russ Allbery ' <rra at stanford dot edu>, "'autoconf at gnu dot org '" <autoconf at gnu dot org>, "'gcc at gcc dot gnu dot org '" <gcc at gcc dot gnu dot org>
- Organization: Santa Cruz Operations
- References: <309F4FC4705DC844987051A517E9E39B16EEBD@red-pt-02.redmond.corp.microsoft.com>
Donn Terry wrote:
>
> Sort of as a poll: on what systems is the getconf
> command not present, and which ones have it but not
> in the default path? Since
> getconf CS_PATH
> is supposed to return the path to the POSIX conforming
That's the path all right. I think the exe name is needed...
CS_PATH The value of the PATH environment variable.
PATH The path through which the shell searches for a specified command.
$ getconf PATH
/bin:/usr/bin
$ getconf CS_PATH
/bin:/usr/bin
This should not be used for autoconf, however, because
someone may be configuring for a private environment.
PATH=`getconf CS_PATH`
inside configure would make that rather difficult. :)
Cheers,
Bruce