Joerg Schilling wrote:
> George Vasick <George.Vasick at Sun.COM> wrote:
>
>> I noticed this potential issue as well. There were two factors in my
>> proposal to leave the Gnu version /usr/bin/cpp:
>>
>> 1) According to the /usr/lib/cpp man page, the preferred way to invoke
>> /usr/lib/cpp is via the cc command rather than invoking it directly.
>
> /usr/lib/cpp is not called by cc because /usr/lib/cc is a K&R cpp.
> It is however called by commands like "rpcgen".
>
>> 2) Section 2.4, 'g' prefixing, of PSARC/2007/047, /usr/gnu, says
>>
>> GNU components that do not conflict with existing or anticipated
>> components in the system's default commands environment should not
>> be placed in /usr/gnu, and do not require 'g'-prefixing.
>>
>> I felt that applied here and proposed to leave the Gnu /usr/bin/cpp as is.
>
> I don't know if commands like rpcgen will call /usr/lib/cpp with absolute
> PATH,
> but GNU cpp's output is incompatible with /usr/lib/cpp
rpcgen invokes cpp via the fully qualified path:
1228: execve("/usr/lib/cpp", 0x08076568, 0x08047CA8) argc = 4
I would expect this to be the case since users do not usually have
/usr/lib in their PATH variables.
There appears to be no conflict with Gnu's /usr/bin/cpp.
Thanks,
George
