Re: [patch] New test+use texinfo @click - @HAVE_MAKEINFO_CLICK@ [Re: doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames)]

[Jan Kratochvil <jan.kratochvil@redhat.com>]

On Tue, 25 Oct 2011 16:26:47 +0200, Joel Brobecker wrote:
> Why do we error out if makeinfo is not available?

As the GDB build errored out by some error later anyway which was moreover not
understandable to the users.


> I think we should do
> the same as other projects such as binutils where we display a warning
> ("makeinfo is missing, documentation will not be built"), and then
> continue. We used to be able to build without requiring makeinfo, and
> installing makeinfo on all machines on our network would be a real pain.
> For us, we know how to work around the problem (configure with
> MAKEINFO=true), but less experience users might not.

As I said in one of the mails I would welcome to be able to build gdb without
makeinfo.  It is always a pain having to install all the texinfo to some slow
exotic arch just to be able to build native gdb there.

I see I could make some mistake but even before the patch of mine above GDB
just was not able to build without makeinfo.  I once tried to fix it - so that
GDB can be built without makeinfo (just not building any doc) but I had some
problems making such patch and as the patch had no business justifications
I just gave up on it.

It would be sure a great patch after the years of pain if you have / could
provide such one.


Thanks,
Jan