From: Joel Brobecker <brobecker@adacore.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Bernd Edlinger <bernd.edlinger@hotmail.de>,
gdb-patches@sourceware.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [ANNOUNCEMENT] GDB 11 release branch created!
Date: Sun, 4 Jul 2021 10:57:33 -0700 [thread overview]
Message-ID: <20210704175733.GA45270@adacore.com> (raw)
In-Reply-To: <87im1q78im.fsf@linux-m68k.org>
[switching to gdb-patches]
> > 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.
Thanks for the heads up, Andreas.
In skimming through the commits, I think the following change is
responsible for this change of behavior:
commit ab954e4a53cab8c33728e6708695abc1616c90b1
Author: Bernd Edlinger <bernd.edlinger@hotmail.de>
Date: Wed Nov 25 18:52:49 2020 +0100
Subject: 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.
2020-12-04 Bernd Edlinger <bernd.edlinger@hotmail.de>
* Makefile.in: Delete GDBvn.texi and version.subst only in
the maintainer-clean target.
I don't understand how this has an impact on building GDB, though.
So, I tried configuring GDB with --with-system-readline, did a "make"
and "make install". It worked with both in-tree and out-of-tree builds.
--
Joel
next parent reply other threads:[~2021-07-04 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20210703175220.9565789AFF@takamaka.home>
[not found] ` <87im1q78im.fsf@linux-m68k.org>
2021-07-04 17:57 ` Joel Brobecker [this message]
2021-07-04 19:00 ` Andreas Schwab
2021-07-04 20:23 ` Joel Brobecker
2021-07-04 20:45 ` Andreas Schwab
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=20210704175733.GA45270@adacore.com \
--to=brobecker@adacore.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.org \
/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