Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess via Gdb <gdb@sourceware.org>
To: Joel Brobecker via Gdb-announce via Gdb <gdb@sourceware.org>,
	gdb@sourceware.org
Cc: Joel Brobecker via Gdb-announce <gdb-announce@sourceware.org>
Subject: Re: [ANNOUNCEMENT] GDB 16.1 released!
Date: Tue, 21 Jan 2025 13:55:45 +0000	[thread overview]
Message-ID: <87tt9smftq.fsf@redhat.com> (raw)
In-Reply-To: <announce.20250118103804.ACAB6803F4@takamaka.gnat.com>

Joel Brobecker via Gdb-announce via Gdb <gdb@sourceware.org> writes:

>             GDB 16.1 released!

Bug https://sourceware.org/bugzilla/show_bug.cgi?id=32578 was reported
against the release.

Consider these steps:

  $ tar -xf gdb-16.1.tar.xz
  $ cd gdb-16.1
  $ mkdir build
  $ cd build
  $ ../configure
  $ make all

This will fail due to issues with the bfd docs; the pre-generated .texi
files are not symlinked into the build tree correctly.

The above is not how we recommend building GDB in gdb/README, our
suggestion is instead:

  $ tar -xf gdb-16.1.tar.xz
  $ cd gdb-16.1
  $ ./configure
  $ make all

This works just fine as the pre-generated .texi files are already in the
expected location, and no symlinks need to be created.

Additionally, in the first case, if you configure with an absolute path
then everything will work fine.

I've posted a fix to the bfd tree here:

  https://inbox.sourceware.org/binutils/40a989ffc81a9b07b5dd70f00521dd2171d7a200.1737465905.git.aburgess@redhat.com

If/when this is merged I do plan to back-port this to the gdb-16-branch,
but given the build following the suggested steps works fine, I'm not
sure this justifies a follow up release.  But I wanted to raise this for
discussion.

Thanks,
Andrew


  reply	other threads:[~2025-01-21 13:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-18 10:38 Joel Brobecker via Gdb-announce via Gdb
2025-01-21 13:55 ` Andrew Burgess via Gdb [this message]
     [not found]   ` <Z5BiYQ6L6bfNZy3M@adacore.com>
2025-01-22  3:20     ` Joel Brobecker via Gdb
2025-01-22 11:02       ` Andrew Burgess via Gdb
2025-01-22 11:07         ` Joel Brobecker via Gdb
2025-01-22 19:55           ` Andrew Burgess via Gdb
2025-01-22 21:22             ` Andrew Burgess via Gdb
2025-01-23  6:29               ` Joel Brobecker via Gdb
2025-01-28 13:04                 ` Andrew Burgess via Gdb
2025-01-29  5:18                   ` Joel Brobecker via Gdb
2025-01-23 18:05             ` Luis Machado via Gdb

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=87tt9smftq.fsf@redhat.com \
    --to=gdb@sourceware.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-announce@sourceware.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