From: Nick Clifton <nickc@redhat.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: jacob navia <jacob@jacob.remcomp.fr>, binutils@sourceware.org
Subject: Re: Trying to install binutils-gdb
Date: Fri, 29 Sep 2023 11:23:06 +0100 [thread overview]
Message-ID: <8b4ae55d-6651-03a2-0180-be439f18531d@redhat.com> (raw)
In-Reply-To: <alpine.BSF.2.20.16.2309272034320.1410@arjuna.pair.com>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
Hi Guys,
On 9/28/23 01:42, Hans-Peter Nilsson wrote:
> This text continues a section that describes how to build from a
> source *tarball*; the "Unpacking and installation" and "When you
> unpack the binutils archive file..."
>
>> 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.
Cheers
Nick
[-- Attachment #2: README.patch --]
[-- Type: text/x-patch, Size: 1960 bytes --]
diff --git a/binutils/README b/binutils/README
index 5120503b80f..82ebd5e774c 100644
--- a/binutils/README
+++ b/binutils/README
@@ -2,12 +2,12 @@
These are the GNU binutils. These are utilities of use when dealing
with binary files, either object files or executables. These tools
-consist of the linker (ld), the assembler (gas), and the profiler
-(gprof) each of which have their own sub-directory named after them.
-There is also a collection of other binary tools, including the
-disassembler (objdump) in this directory. These tools make use of a
-pair of libraries (bfd and opcodes) and a common set of header files
-(include).
+consist of the linkers (ld and gold), the assembler (gas), and the
+profiler (gprof and gprofng) each of which have their own
+sub-directory named after them. There is also a collection of other
+binary tools, including the disassembler (objdump) in this directory.
+These tools make use of a pair of libraries (bfd and opcodes) and a
+common set of header files (include).
There are README and NEWS files in most of the program sub-directories
which give more information about those specific programs.
@@ -44,6 +44,20 @@ You can just do:
This will configure and build all the libraries as well as the
assembler, the binutils, and the linker.
+Note - if you have obtained the sources by checking out a copy from
+the git repository then you will have both the binutils and GDB
+sources in one place. In this case you may wish to add an option to
+the configure command line to stop it from configuring GDB. This will
+also stop the configure script from checking the libraries that are
+needed by GDB, but not by the binutils.
+
+ ./configure --disable-gdb
+
+Since the configure script can be quite verbose, you may also
+want to add the --quiet option to reduce the amount of output. ie:
+
+ ./configure --quiet
+
If you have GNU make, we recommend building in a different directory:
mkdir objdir
next prev parent reply other threads:[~2023-09-29 10:23 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 [this message]
2024-01-28 19:30 ` Maciej W. Rozycki
2024-01-29 8:52 ` Guinevere Larsen
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=8b4ae55d-6651-03a2-0180-be439f18531d@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=hp@bitrange.com \
--cc=jacob@jacob.remcomp.fr \
/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).