public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Andreas Schwab <schwab@linux-m68k.org>,
	Joel Brobecker <brobecker@adacore.com>,
	Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tom@tromey.com>,
	Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 11 release branch created!
Date: Mon, 5 Jul 2021 12:36:00 +0200	[thread overview]
Message-ID: <78ca1c45-beb3-966f-e995-912bc1e115c1@suse.de> (raw)
In-Reply-To: <87im1q78im.fsf@linux-m68k.org>

On 7/4/21 11:06 AM, Andreas Schwab wrote:
> On Jul 03 2021, Joel Brobecker wrote:
> 
>> The prerelease snapshots will be available at:
>>
>>     ftp://sourceware.org/pub/gdb/snapshots/branch/gdb.tar.xz
> 
> The tarball contains the file gdb/doc/GDBvn.texi which is a generated
> file depending on the configuration.  This breaks building with
> --with-system-readline.

Hi,

I managed to reproduce this.

The steps are:
- download (or create using src-release.sh) a snapshot
- unpack it, into say src
- cd src; find -name "*.info*" | xargs rm -f
- mkdir build; cd build ; ../src/configure --with-system-readline
- cd build; make all-gdb

For make output, see below.

This can be fixed/worked around by doing:
...
$ rm -f gdb/doc/GDBvn.texi
...
as Andreas did here (
https://build.opensuse.org/package/rdiff/home:AndreasSchwab/gdb?linkrev=base&rev=143
).

My guess is that this is a regression since:
...
commit ab954e4a53cab8c33728e6708695abc1616c90b1
Author: Bernd Edlinger <bernd.edlinger@hotmail.de>
Date:   Wed Nov 25 18:52:49 2020 +0100

    Fix building gdb release from tar file without makeinfo

    Add GDBvn.texi and version.subst to the release tar file,
    so the gdb.info does not need makeinfo.

    This avoids the need for makeinfo to be available.
...

Interestingly, there are previous commits related to GDBvn.texi where
the submission emails show the same problem (
https://sourceware.org/pipermail/gdb-patches/2011-January/078980.html ),
and the final conclusion of that discussion (
https://sourceware.org/pipermail/gdb-patches/2011-January/079001.html ) is:
...
So, unless anyone else objects, removing GDBvn.texi from the
distributed files is the solution.
...

Thanks,
- Tom

...
make[2]: Entering directory '/home/vries/upstream/tmp/build/gdb'
make[3]: Entering directory '/home/vries/upstream/tmp/build/gdb/doc'
(test "ln -s" = "ln -s" && \
  ln -s ../../../src/gdb/doc/all-cfg.texi gdb-cfg.texi) || \
ln ../../../src/gdb/doc/all-cfg.texi gdb-cfg.texi || \
cp ../../../src/gdb/doc/all-cfg.texi gdb-cfg.texi
makeinfo --split-size=5000000  -DHAVE_MAKEINFO_CLICK  -I
../../../src/gdb/doc/../mi -I ../../../src/gdb/doc \
        -o gdb.info ../../../src/gdb/doc/gdb.texinfo
../../../src/gdb/doc/gdb.texinfo:38160: @include: could not find rluser.texi
../../../src/gdb/doc/gdb.texinfo:38161: @include: could not find hsuser.texi
../../../src/gdb/doc/gdb.texinfo:25774: @xref reference to nonexistent
node `Command Line Editing'
../../../src/gdb/doc/gdb.texinfo:25806: @xref reference to nonexistent
node `Using History Interactively'
../../../src/gdb/doc/gdb.texinfo:25902: @xref reference to nonexistent
node `Event Designators'
../../../src/gdb/doc/gdb.texinfo:28508: @pxref reference to nonexistent
node `Command Line Editing'
../../../src/gdb/doc/gdb.texinfo:172: @menu reference to nonexistent
node `Command Line Editing'
../../../src/gdb/doc/gdb.texinfo:173: @menu reference to nonexistent
node `Using History Interactively'
make[3]: *** [Makefile:491: gdb.info] Error 1
make[3]: Leaving directory '/home/vries/upstream/tmp/build/gdb/doc'
make[2]: *** [Makefile:1973: subdir_do] Error 1
make[2]: Leaving directory '/home/vries/upstream/tmp/build/gdb'
make[1]: *** [Makefile:1639: all] Error 2
make[1]: Leaving directory '/home/vries/upstream/tmp/build/gdb'
make: *** [Makefile:10116: all-gdb] Error 2
...

  reply	other threads:[~2021-07-05 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 17:52 Joel Brobecker
2021-07-04  9:06 ` Andreas Schwab
2021-07-05 10:36   ` Tom de Vries [this message]
2021-07-05 12:33     ` Eli Zaretskii
2021-07-05 13:36       ` Tom de Vries
2021-07-05 15:34         ` Eli Zaretskii
2021-07-06 14:58           ` Tom de Vries
2021-07-06 15:50             ` 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=78ca1c45-beb3-966f-e995-912bc1e115c1@suse.de \
    --to=tdevries@suse.de \
    --cc=bernd.edlinger@hotmail.de \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=schwab@linux-m68k.org \
    --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).