Re: [PATCH v1 2/4] config.mak.uname: support for modern HPE NonStop config.
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 28, 2018, 20:07 UTC
- Message-ID
- <xmqqa7kpmmtj.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <000601d49e0b$e11d7520$a3585f60$@rogers.com>
"Randall S. Becker" <randall.s.becker@rogers.com> writes:
Show 22 quoted lines
> On December 27, 2018 12:03, Eric Sunshine wrote:
>> On Wed, Dec 26, 2018 at 6:05 PM <randall.s.becker@rogers.com> wrote:
>> > A number of configuration options are not automatically detected by
>> > configure mechanisms, including the location of Perl and Python.
>> > [...]
>> > Signed-off-by: Randall S. Becker <rsbecker@nexbridge.com>
>> > ---
>> > diff --git a/config.mak.uname b/config.mak.uname @@ -441,26 +441,45
>> @@
>> > ifeq ($(uname_S),NONSTOP_KERNEL)
>> > # Our's are in ${prefix}/bin (perl might also be in /usr/bin/perl).
>> > - PERL_PATH = ${prefix}/bin/perl
>> > - PYTHON_PATH = ${prefix}/bin/python
>> > + PERL_PATH = /usr/bin/perl
>> > + PYTHON_PATH = /usr/bin/python
>>
>> Is the in-code comment about ${prefix} still applicable after this change?
>
> The ${prefix} is not applicable on this platform for perl and
> python. Those locations must be in /usr/bin and are managed by the
> Operating System vendor not by customers. The change is wrapped in
> an IF so is only applicable to NonStop.So the answer is "Our's are in ${prefix}/bin..." is no longer correct? If so, this patch must remove that stale comment at the same time, no?