Run time path configuration

[Jason Merrill]

>>>>> Jeffrey A Law <law@cygnus.com> writes:

>   In message < 4825664E.00415DE7.00@nyc-ntgw-n01.ny.jpmorgan.com >you write:
>> Lastly, why does cccp.c continue to exist when cpplib appears to do
>> the same thing, and must be out of nappies (U.S. diapers?)  by now?  Can I
>> ignore it by using some cunning set of config options?

> Because "cpplib" is not yet fully functional.  Plus we still have todeal
> with lame systems that want to call "cpp" directly.

That's not an issue; see cppmain.c.

Jason