public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Nick Clifton <nickc@redhat.com>
Cc: jacob navia <jacob@jacob.remcomp.fr>, binutils@sourceware.org
Subject: Re: Trying to install binutils-gdb
Date: Wed, 27 Sep 2023 20:42:31 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSF.2.20.16.2309272034320.1410@arjuna.pair.com> (raw)
In-Reply-To: <efa27460-9e95-63c3-c00f-da645342f2d0@redhat.com>

On Wed, 27 Sep 2023, Nick Clifton via Binutils wrote:

> Hi Jacob,
> 
> > I downloaded the new version of binutils.
> > To my surprise, it doesn?t work any more, failing with a message that I
> > should get the GMP package.
> 
> This is really a documentation issue.  I assume that you
> were following the instructions in the binutils/README file
> on how to unpack and install the binutils ?  I am thinking
> of changing that section of the file to read like this:
> 
> -------------------------------------------------------------
> [...]

>   To build binutils you will need a C99 compliant compiler and library.
>   You can just do:

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:" [...]

brgds, H-P

  reply	other threads:[~2023-09-28  0:42 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 [this message]
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

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=alpine.BSF.2.20.16.2309272034320.1410@arjuna.pair.com \
    --to=hp@bitrange.com \
    --cc=binutils@sourceware.org \
    --cc=jacob@jacob.remcomp.fr \
    --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).