public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "Old, Oliver" <Oliver.Old@loewen.de>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: GDB configuration for multi-arch
Date: Tue, 12 Dec 2023 18:38:10 +0000	[thread overview]
Message-ID: <3766c6fa-f14a-43dc-8847-87a5d8e6afea@dronecode.org.uk> (raw)
In-Reply-To: <VI1PR03MB35365B66D1C92C17C1642C548DD7A@VI1PR03MB3536.eurprd03.prod.outlook.com>

On 16/10/2023 17:14, Old, Oliver via Cygwin wrote:
> Good evening!
> 
> The difference in size is indeed a whopping 19M (8M -> 27M). That might be why the Msys devs chose to split their gdb into a main package and a multi-arch package that depends on the main package.
> 
> In case you decide to build gdb with 'enable-targets=all', definitely also configure with '--disable-sim' or it'll build simulators for the additional architectures.

I (finally) got around to looking at this.

The gdb 14.1 test release includes a separate gdb-multiarch package, 
with gdb built with '--enable-targets=all'.

I didn't get to do anything fancy with alternatives symlinks, so you'll 
need to explicitly run the 'gdb-multiarch' executable.

> This is just an oversight, I think.
> 
> I'll look at adding that for the forthcoming gdb 14.1, assuming it
> doesn't make the package ridiculously larger.


           reply	other threads:[~2023-12-12 18:38 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <VI1PR03MB35365B66D1C92C17C1642C548DD7A@VI1PR03MB3536.eurprd03.prod.outlook.com>]

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=3766c6fa-f14a-43dc-8847-87a5d8e6afea@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Oliver.Old@loewen.de \
    --cc=cygwin-apps@cygwin.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).