From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 7BZDN4ZsMGIodAAAWB0awg (envelope-from ) for ; Tue, 15 Mar 2022 06:37:58 -0400 Received: by simark.ca (Postfix, from userid 112) id B0F8B1F3CE; Tue, 15 Mar 2022 06:37:58 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_DYNAMIC, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 8C0E91F0D2 for ; Tue, 15 Mar 2022 06:37:57 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id A47D53858010 for ; Tue, 15 Mar 2022 10:37:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A47D53858010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1647340676; bh=Wcl8X/e1E5d31WRgsHzSGHIkTgzyK+v1MbZHt+f563A=; h=Date:To:References:Subject:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=BbYC3YTCZwHNzBHkFrzu+0i1Aepg52LwA1n8r8b1leDkWGjlP/RaNZlNAq0aJBoY+ dOIPie00CXDVbvGkH+apJCATpfFXTxK2aPhT3+mj5rmmuVr04VMlp4GijE/6yHinNn mrNUGrwO/XMBS1rzfcvSRPayeT5Gk2iNbmzwC1T4= Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id 8FDEC3858D28 for ; Tue, 15 Mar 2022 10:37:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8FDEC3858D28 Received: from [2001:470:142:3::e] (port=33988 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nU4YU-0006uJ-Qh; Tue, 15 Mar 2022 06:37:30 -0400 Received: from ip5f5a87b5.dynamic.kabel-deutschland.de ([95.90.135.181]:63654 helo=[192.168.111.41]) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nU4YU-0008UL-Gk; Tue, 15 Mar 2022 06:37:30 -0400 Message-ID: <5ef7f88e-f427-6c6f-0a4b-b63abbe4c8d3@gnu.org> Date: Tue, 15 Mar 2022 11:37:26 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 To: brobecker@adacore.com, luis.machado@arm.com References: Content-Language: en-US Subject: Re: --with-gmp and --with-libgmp-prefix In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: , From: Simon Sobisch via Gdb Reply-To: Simon Sobisch Cc: gdb@sourceware.org Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" On 3/11/22 10:06, Joel Brobecker wrote: >> I was talking to a colleague and we noticed the top-level binutils- >> gdbconfigure 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. [...] >> >> 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. > 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. Hm, maybe in this case one can opt for the binutils style with keeping the GDB one "for compat"? In theory this would add one additional "feature" - the possibility to specify the header and library path independently. In this case the help for -with-libgmp-prefix could just say something like "alias for --with-gmp". Just saying... Simon