From: Nick Clifton <nickc@redhat.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
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 16:50:23 +0000 [thread overview]
Message-ID: <8e635342-8479-40da-8158-41713010b7f4@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2401281915050.15781@angie.orcam.me.uk>
Hi Maciej,
> $ ./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,
I think that that would be a good idea, at least until your suggestion
below is implemented.
> 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.
To make things simpler, I think that it might be better to have users
'enable' the tool that they want. ie:
"configure --enable-gdb" just configure gdb and friends
"configure --enable-binutils" just configures the binutils stuff
We might even make it so that if neither of these options are given then
configure prints: "configuring both GDB and BINUTILS, is this really what you want ?"
or something like that.
Cheers
Nick
prev parent reply other threads:[~2024-01-29 16:50 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
2024-01-29 16:50 ` Nick Clifton [this message]
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=8e635342-8479-40da-8158-41713010b7f4@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hp@bitrange.com \
--cc=jacob@jacob.remcomp.fr \
--cc=macro@orcam.me.uk \
/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).