From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx07-00178001.pphosted.com (mx07-00178001.pphosted.com [185.132.182.106]) by sourceware.org (Postfix) with ESMTPS id A55EF3858D20 for ; Thu, 31 Aug 2023 14:01:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A55EF3858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=foss.st.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=foss.st.com Received: from pps.filterd (m0241204.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.17.1.22/8.17.1.22) with ESMTP id 37V8dipK014919; Thu, 31 Aug 2023 16:01:38 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h= message-id:date:mime-version:subject:to:references:from :in-reply-to:content-type:content-transfer-encoding; s= selector1; bh=/SpjuxNHJn1qcAq0xdDTrXnZm1/qQ6C8FkxfLzpD8mc=; b=06 S6D+fDPxn8tN4BvbZEdO5phB6UnsoOnddkq6dm6z8S7trjgdRMSVOcl9eIHRztVJ wrzNL46f0BLnOv9ts3kCptAjdX/k5LtNPVhIHz1Dn5IDlmemavxYpWBn1DrA2TmL ZcHIJe4tfaQ6hwBWQt5TvKtHg4Ed8HhMRoQAjPjGynWMLQ9eF1kEOSUttAwy57c3 DDMjDUDhQtzZgaM3yGyDs7IJT+FLDoMvTet/G8flDA8MPhrPMQbi9ko4lImrj+gk p1wwrdfoTVcZQJrlkSob32k9tQ0F6MqUzK+wuAugunK6dfPsTkkqwzSyizeANlnC hGrb4kWaMuKnAnAhNrFw== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com (PPS) with ESMTPS id 3sq8qwnkk4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 31 Aug 2023 16:01:38 +0200 (MEST) Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id EE57D100056; Thu, 31 Aug 2023 16:01:36 +0200 (CEST) Received: from Webmail-eu.st.com (shfdag1node3.st.com [10.75.129.71]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 850D12132F1; Thu, 31 Aug 2023 16:01:36 +0200 (CEST) Received: from [10.252.18.91] (10.252.18.91) by SHFDAG1NODE3.st.com (10.75.129.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Thu, 31 Aug 2023 16:01:35 +0200 Message-ID: <0007c884-16a1-2fe3-e574-d9fe5c944c83@foss.st.com> Date: Thu, 31 Aug 2023 16:01:34 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: GDB13 fails to build on MacOS using supplied GNU Bison 2.3 Content-Language: en-US To: Tom Tromey , Torbjorn SVENSSON via Gdb References: <0badf084-d0b7-54bb-aec6-b79f29ad191d@foss.st.com> <87jztbpccn.fsf@tromey.com> From: Torbjorn SVENSSON In-Reply-To: <87jztbpccn.fsf@tromey.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.252.18.91] X-ClientProxiedBy: EQNCAS1NODE4.st.com (10.75.129.82) To SHFDAG1NODE3.st.com (10.75.129.71) X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.957,Hydra:6.0.601,FMLib:17.11.176.26 definitions=2023-08-31_12,2023-08-31_01,2023-05-22_02 X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hello Tom, On 2023-08-31 15:31, Tom Tromey wrote: >>>>>> "Torbjorn" == Torbjorn SVENSSON via Gdb writes: > > Torbjorn> All three versions of MacOS includes GNU Bison 2.3 and it appears that > Torbjorn> this issue was fixed in GNU Bison 2.4. > > If the appended works for you (be sure to run some tests), I can check > it in. Not sure what you mean by "appended" here... I see no attachment and my mail clarily stated that I could not generate the configure script using the autotools. > Torbjorn> Looking at the binutils tree, I see that sub-directory gprofng > Torbjorn> contains bison.m4 and a check to confirm that at least version 3.0.4 > Torbjorn> is available. > > Torbjorn> I think the bison.m4 file should be moved up one level and used in > Torbjorn> both gprofng and gdb, but I'm unable to re-generate the configure > Torbjorn> scripts. > > I wonder if this would really help you, since presumably it would just > reject your bison? Well, what I was thinking was to have something telling the user that the sources requires version x.y of bison rather than silently breaking during the compile stage with some obscure error message. > Another option might be to install bison from brew. In this case it's > probably fine but eventually we may want to require a newer Bison, and > IMO we can't and shouldn't keep catering to Apple's problem > indefinitely. Yes, this is how I solved it on out system, but it's still not as helpful as a configure error would have been to let others know that the bison version is too old... Regards, Torbjörn