From: Pedro Alves <pedro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>,
eliz@gnu.org
Subject: Re: [patch] New test+use texinfo @click - @HAVE_MAKEINFO_CLICK@ [Re: doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames)]
Date: Wed, 12 Oct 2011 15:26:00 -0000 [thread overview]
Message-ID: <201110121626.24835.pedro@codesourcery.com> (raw)
In-Reply-To: <20111011233417.GA17487@host1.jankratochvil.net>
On Wednesday 12 October 2011 00:34:17, Jan Kratochvil wrote:
> On Mon, 10 Oct 2011 23:56:34 +0200, Pedro Alves wrote:
> > On Monday 10 October 2011 19:47:26, Jan Kratochvil wrote:
> > > + if makeinfo conftest.texinfo >&5 2>&5; then
> >
> > Shouldn't this be $(MAKEINFO) instead (like in Makefile.in)?
> > Though I'm not sure how to do that here. Maybe
> > AC_CHECK_PROGS(MAKEINFO, makeinfo) ?
>
> Yes, it should, although it is more complicated.
>
> There is IMO a bug in toplevel configure it does not pass down MAKEINFOFLAGS
> and includes "--split-size=5000000" directly into MAKEINFO. Without the
> special handling of --split-size=5000000 it would be used during first
> compilation but no longer used after automatic re-run of configure in gdb/
> (although only if one deletes gdb/config.cache).
I see. We should get that fixed someday.
> Therefore I added --split-size=5000000 there explicitly, which means it is
> duplicated during the dirst compilation but it does not matter.
>
> --split-size=5000000 was not used in gdb/doc/ before at all but I think it was
> a bug, even gcc uses --no-split.
No opinion on that.
> On Tue, 11 Oct 2011 00:18:54 +0200, Andreas Schwab wrote:
> > You should not modify MAKEINFO. If you say
> > "make info MAKEINFO=/usr/local/bin/makeinfo" you lose the flags.
>
> True, toplevel configure is already violating that but fixed it in gdb/ .
Thanks. Looks good to me.
--
Pedro Alves
next prev parent reply other threads:[~2011-10-12 15:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 19:50 [patch 04/12] entryval#3: Virtual tail call frames Jan Kratochvil
2011-10-09 19:27 ` [commit] " Jan Kratochvil
2011-10-09 20:23 ` Jan Kratochvil
2011-10-10 13:40 ` doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames) Ulrich Weigand
2011-10-10 13:54 ` Eli Zaretskii
2011-10-10 13:58 ` Ulrich Weigand
2011-10-10 14:58 ` [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
2011-10-10 15:16 ` Pedro Alves
2011-10-10 15:31 ` Jan Kratochvil
2011-10-10 15:51 ` Pedro Alves
2011-10-10 18:47 ` Jan Kratochvil
2011-10-10 19:11 ` Eli Zaretskii
2011-10-10 21:56 ` Pedro Alves
2011-10-10 22:19 ` Andreas Schwab
2011-10-11 23:34 ` Jan Kratochvil
2011-10-12 15:26 ` Pedro Alves [this message]
2011-10-12 15:56 ` Jan Kratochvil
2011-10-25 14:35 ` Joel Brobecker
2011-10-25 14:47 ` Jan Kratochvil
2011-10-25 16:09 ` Joel Brobecker
2011-10-10 16:10 ` Eli Zaretskii
2011-10-10 16:15 ` Jan Kratochvil
2011-10-10 16:09 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201110121626.24835.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=schwab@linux-m68k.org \
--cc=uweigand@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox