> Date: Sun, 05 Jul 2009 00:33:44 +0100 > From: Dave Korn <dave.korn.cyg...@googlemail.com> > CC: Eli Zaretskii <e...@gnu.org>, gcc@gcc.gnu.org > > >> e...@fencepost:~$ gcc -print-prog-name=cpp > >> cpp > > > > Yeah, that's a clear doc bug. It used to work with "cpp", but not with > > current gcc releases. > > > >> Similarly, it doesn't work with `gcc' itself, which seems a pity, > >> as it doesn't allow to write scripts that discover where GCC > >> lives. > > > > If you are using cachecc or distcc, the question of where GCC lives is > > somewhat ambiguous in any case. > > Well, the simple rule is "It can tell you where any program that gcc might > invoke lives", isn't it? That would explain why it can locate cc1, ld and as, > but not gcc or ls, and why it used to be able to locate cpp when it used to > invoke cpp, but not since.
Granted, I know very well why it doesn't work with cpp and gcc. But I was talking about _user_documentation_, and from the user's point of view (as opposed to GCC programmer/hacker POV), the distinction is not quite obvious. Either the docs should be fixed to make that clear, or (better) the code should be modified to support all related programs.
