public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Andrea Monaco via Gdb <gdb@sourceware.org>
Cc: simark@simark.ca,  Andrea Monaco <andrea.monaco@autistici.org>
Subject: Re: gdb 11.1: configure doesn't check for gmp existence
Date: Mon, 01 Nov 2021 23:48:56 +0100	[thread overview]
Message-ID: <yddmtmnze3r.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87ilxb8qno.fsf@autistici.org> (Andrea Monaco via Gdb's message of "Mon, 01 Nov 2021 23:19:55 +0100")

Hi Andrea,

>   > Can you show the error you get?  Normally, when you type "make" at
>   > the top-level that will run the configure script in the gdb
>   > directory, and that's when it should fail.
>
> Upon check, yes, that's what happens.  But it's an unusual build system:
> it's common to have Makefiles in subdirectories, while multiple
> configures are less common.
>
> Anyway, if gmp is an essential dependency, why does the top-level
> configure complete without it?

it's also unlike GCC's gmp (and mpfr and mpc) detection which is done at
the toplevel and errors out if one of the necessary components is either
missing or too old.  Not only does GDB use a different way of detecting
support libraries, but also a less capable one than GCC's (cf. PR
build/28332 for a regression caused by that).  It's also confusing to
users familiar with GCC's configure options for gmp etc. location: they
are present but have no effect.  Not the best user experience, I'd
argue.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

      reply	other threads:[~2021-11-01 22:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 15:58 Andrea Monaco
2021-11-01 20:39 ` Simon Marchi
2021-11-01 22:19 ` Andrea Monaco
2021-11-01 22:48   ` Rainer Orth [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=yddmtmnze3r.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=andrea.monaco@autistici.org \
    --cc=gdb@sourceware.org \
    --cc=simark@simark.ca \
    /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).