public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>,
	Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH][gdb/build] Add gdb/contrib/makeinfo-dummy.sh
Date: Tue, 4 Oct 2022 17:37:59 +0200	[thread overview]
Message-ID: <3ef424f2-f0f6-e470-01cb-b8990f5489d7@suse.de> (raw)
In-Reply-To: <87illh6etu.fsf@tromey.com>

On 9/20/22 21:11, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> Tom> I gave the --without-makeinfo a try.
> 
> Tom> WDYT?
> 
> It seems reasonable to me.

Thanks for the review.

I've posted it to the gcc ml: 
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/602797.html .

> FWIW I think there is at least one bug in bugzilla on this topic.

There's https://sourceware.org/bugzilla/show_bug.cgi?id=14678 which is 
mostly about the GDBvn.texi issue, which should already be fixed by 
commit ab954e4a53c ("Fix building gdb release from tar file without 
makeinfo").

But there's indeed duplicate 
https://sourceware.org/bugzilla/show_bug.cgi?id=20417 which does mention 
--without-makeinfo.

Thanks,
- Tom

      reply	other threads:[~2022-10-04 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  9:51 Tom de Vries
2022-09-01 14:43 ` Simon Marchi
2022-09-01 14:58   ` Tom de Vries
2022-09-01 17:21     ` Simon Marchi
2022-09-05 14:10       ` Tom de Vries
2022-09-20 19:11         ` Tom Tromey
2022-10-04 15:37           ` Tom de Vries [this message]

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=3ef424f2-f0f6-e470-01cb-b8990f5489d7@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).