Re: [doc] Avoid conflicts between gdb and cross-gdb.

[Doug Evans <dje@google.com>]

On Wed, Aug 6, 2014 at 12:53 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> > I just found it odd that you'd do "man powerpc-elf-gdb" but then do
>> > "info gdb", even if the debugger you have is called
>> > "powerpc-elf-gdb".
>>
>> That's true, but the main motivation for the issue at hand was
>> "make uninstall", which I think doesn't apply to the Info manual.
>
> I am not sure I understand why gdb.info is any different from
> man/gdb.X in that respect. If I do:
>
>   % cd /path/to/native-gdb/build
>   % make install
>   % cd /path/to/cross-gdb/build
>   % make install
>
> ... and then do ...
>
>   % make uninstall
>
> ... wouldn't that delete gdb.info?

Yeah, but it would also delete all the, e.g., python files (absent
configure args to put them in separate places, but then the sharing is
gone).

So either "make uninstall" has to work differently in a shared
context, or there can be no sharing, or accept the issue and maybe
provide another uninstall rule to skip possibly shared files.

Though reading the original post I'm not sure "make uninstall" was the
main motivation here, rather that the installed man page should match
the installed binary name (and if one went that route then "make
uninstall" would need similar changes).  Could have misread though.

Do we really need to install ${target}-gdb.1 ?