From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>,
Sergei Trofimovich <slyfox@gentoo.org>,
Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, Sergei Trofimovich <siarheit@google.com>
Subject: Re: [PATCH] gdb: fix IA64 build failure of linux-nat
Date: Mon, 17 Aug 2020 04:21:40 -0400 [thread overview]
Message-ID: <a060b319-d851-4074-c2f0-2f8d354cb4e0@simark.ca> (raw)
In-Reply-To: <5f684182-c8d5-744b-8486-18f89ffb30a3@suse.de>
On 2020-08-17 4:54 a.m., Tom de Vries wrote:
> Hi,
>
> IA64 support was just obsoleted in bfd (commit 73d0dc162e "Obsolete ia64").
>
> So, AFAIU, this should now be built with --enable-obsolete.
>
> What are the consequences for gdb IA64 patches ?
>
> Thanks,
> - Tom
By transitivity, I'd say that the GDB port is also obsolete. But as long as it's in
the tree, it's fine to accept patches to keep it building (otherwise it's useless to
keep it in the tree).
If you wanted to build GDB with --target=ia64-something-something, you'll need to pass
--enable-obsolete in order to build BFD, which is a required dependency of GDB. When we
pass --enable-targets=all, it builds a GDB with ia64 support without requiring that
--enable-obsolete flag though.
Do you know what's the BFD policy for obsolete configurations? If they wanted to get
rid of it completely, they would need to remove GDB support too, otherwise they'd break
the build. So should we eventually take the lead and remove support for it first?
Sergei, quick survey: do you, or someone you know actually use GDB on ia64? Or you just
noticed it not building because you package it?
Simon
next prev parent reply other threads:[~2020-08-17 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 21:27 Sergei Trofimovich
2020-05-19 22:00 ` Kevin Buettner
2020-08-16 8:45 ` Sergei Trofimovich
2020-08-16 21:51 ` Simon Marchi
2020-08-17 8:54 ` Tom de Vries
2020-08-17 8:21 ` Simon Marchi [this message]
2020-08-17 18:59 ` Sergei Trofimovich
2020-08-18 8:46 ` Tom de Vries
2020-08-17 20:57 ` Sergei Trofimovich
2020-08-17 21:04 ` Simon Marchi
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=a060b319-d851-4074-c2f0-2f8d354cb4e0@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=siarheit@google.com \
--cc=slyfox@gentoo.org \
--cc=tdevries@suse.de \
/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