public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Guinevere Larsen <blarsen@redhat.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>, Nick Clifton <nickc@redhat.com>
Cc: Hans-Peter Nilsson <hp@bitrange.com>,
	jacob navia <jacob@jacob.remcomp.fr>,
	binutils@sourceware.org, gdb@sourceware.org
Subject: Re: Trying to install binutils-gdb
Date: Mon, 29 Jan 2024 09:52:42 +0100	[thread overview]
Message-ID: <0c5d519f-8255-46f6-a71d-78353a80bb01@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2401281915050.15781@angie.orcam.me.uk>

On 28/01/2024 20:30, Maciej W. Rozycki wrote:
> On Fri, 29 Sep 2023, Nick Clifton via Binutils wrote:
>
>>>>     If you only want to build the binutils and not GDB as well then
>>>>     you can add a configure option to disable GDB.  This may help
>>>>     reduce the need for extra libraries to be installed.  ie:
>>>>
>>>> 	./configure --disable-gdb
>>> ...so this step would then be confusing.
>>>
>>> IMHO it needs to say something like "if you build from a
>>> checkout of the binutils-gdb git, you may also want to build
>>> only binutils and exclude gdb, like so:" [...]
>> That makes sense.  I have checked in the following updated patch instead.
>   I have only come across this message now.
>
>   Note that nowadays we have other GDB components at the top level, most
> notably `gdbserver', as well as the GNU simulator, all of which are a part
> of the GDB project.  So to build parts that comprise binutils only from a
> git checkout you really need to disable more, such as with:
>
> $ ./configure --disable-gdb --disable-gdbserver --disable-libbacktrace \
>    --disable-libdecnumber --disable-readline --disable-sim
>
> This is what I have been doing with my builds.
>
>   I'll be happy to offer a patch if this turns out how we want to update
> binutils/README further, however it seems to me that we probably want to
> have a pair of umbrella options, say `--disable-gdb-components' and
> `--disable-binutils-components', to let people choose more easily what
> project they want to build from a checkout without the need to dive into
> individual components and also possibly without having to keep track of
> what new components get added as they upgrade.  There'd be a slight
> maintenance burden for such options though.

yes please!

I can never remember all the components that I need to disable from 
binutils to get as quick a compilation as possible. I am still not sure 
if I did disable everything or if copying my previous configure run 
isn't accidentally building some parts unnecessarily. I'm not sure if I 
personally like the `-components` suffix, but I don't have any better 
suggestions.

-- 
Cheers,
Guinevere Larsen
She/Her/Hers

>
>   Cc-ing the GDB mailing list for any input from the other camp.
>
>    Maciej
>


  reply	other threads:[~2024-01-29  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 19:51 jacob navia
2023-09-26 21:49 ` Arsen Arsenović
2023-09-27 14:42 ` Nick Clifton
2023-09-28  0:42   ` Hans-Peter Nilsson
2023-09-29 10:23     ` Nick Clifton
2024-01-28 19:30       ` Maciej W. Rozycki
2024-01-29  8:52         ` Guinevere Larsen [this message]
2024-01-29 16:50         ` Nick Clifton

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=0c5d519f-8255-46f6-a71d-78353a80bb01@redhat.com \
    --to=blarsen@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=hp@bitrange.com \
    --cc=jacob@jacob.remcomp.fr \
    --cc=macro@orcam.me.uk \
    --cc=nickc@redhat.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).