From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) by sourceware.org (Postfix) with ESMTPS id 839F13858D3C for ; Fri, 11 Mar 2022 10:06:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 839F13858D3C Received: by mail-wr1-x434.google.com with SMTP id q14so12160598wrc.4 for ; Fri, 11 Mar 2022 02:06:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=cCV6ocuFXQPl6Sah6BqxOSHdM76PuyBielcoaoxYbUM=; b=3ujRfBZdDpldPuL5KyzRNvcJbxgDOGNws9kxJonKdXD6OY3s0kRVdOL25IzvBBMVsF x+5zMC3BMZSmVyJr6GI/NEt56F0PnCGtMvYTrk3lgNSmbvn301zEr81Y67saoj/d4Cpy kozad/vPgQi2fdWY/SyRvmJ4c6PGOqiqEfPKSQhOYbDGpZs8IRvhD3icZEUZeLWYhnrQ zJMwsYBh8al8n+aGX5sgyCKJEbx5Sj3L4Y87wKrn1fySxBQPSCT2ikpEpFCyWt5DpHc/ riuJped6/cVNdmxhlcXc2vCC2rRCtLo3dOMZzX5RwoXE7SqA407G7/c8hKeLS4YywBNA zFvg== X-Gm-Message-State: AOAM530bzmemmKKW4B7PEZzdmTWyfru6PajYeBgATqCDBgGPE0SkHb2/ KTo7INsxgFDna1/1YmFnDWivRAJcvBzd X-Google-Smtp-Source: ABdhPJxHGKTwLef/9kYnNiTpLl2vcSKrfmKjX6DqHAt9NbcHPrBteMLQGupsQl7QsARbrCBdWAXRDg== X-Received: by 2002:a5d:51cd:0:b0:1f0:1c03:5236 with SMTP id n13-20020a5d51cd000000b001f01c035236mr6779865wrv.195.1646993175240; Fri, 11 Mar 2022 02:06:15 -0800 (PST) Received: from takamaka.home (lfbn-reu-1-503-119.w92-130.abo.wanadoo.fr. [92.130.90.119]) by smtp.gmail.com with ESMTPSA id p12-20020a056000018c00b001f079518150sm6476565wrx.93.2022.03.11.02.06.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 11 Mar 2022 02:06:14 -0800 (PST) Received: by takamaka.home (Postfix, from userid 1000) id 4E6C0A4AD3; Fri, 11 Mar 2022 14:06:12 +0400 (+04) Date: Fri, 11 Mar 2022 14:06:12 +0400 From: Joel Brobecker To: Luis Machado Cc: gdb@sourceware.org, Joel Brobecker Subject: Re: --with-gmp and --with-libgmp-prefix Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2022 10:06:18 -0000 > I was talking to a colleague and we noticed the top-level binutils-gdb > configure accepts --with-gmp, which looks like what gcc's configure uses to > specify the gmp library installation path. > > But gdb's configure expects that information to be passed through the > --with-libgmp-prefix switch. Was that a deliberate choice (I'm looking at > commit 2c947d9bc2ff3b84f1676b83577fe1bba05b4a5f). > > When one is used to building gcc, it is a little odd to have to specify > --with-libgmp-prefix instead of --with-gmp. > > The top-level configure lists this: > > --with-gmp=PATH specify prefix directory for the installed GMP > package. Equivalent to > --with-gmp-include=PATH/include plus > --with-gmp-lib=PATH/lib > > And gdb's configure lists this: > > --with-libgmp-prefix[=DIR] search for libgmp in DIR/include and DIR/lib > > I'm wondering if we can reuse the top-level configure's --with-gmp option. Deja vu ;-) The problem is that GDB has some shared configury that follows a certain style, which is not the style that is used by the toplevel configury. This triggered a number of discussions, but in the end we found no good solution, unfortunately. -- Joel