From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3412 invoked by alias); 19 Dec 2011 15:08:17 -0000 Received: (qmail 3403 invoked by uid 22791); 19 Dec 2011 15:08:16 -0000 X-SWARE-Spam-Status: No, hits=-5.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 19 Dec 2011 15:07:52 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pBJF7piT022765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Dec 2011 10:07:51 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id pBJF7pvV005084; Mon, 19 Dec 2011 10:07:51 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id pBJF7nM9032527; Mon, 19 Dec 2011 10:07:50 -0500 From: Tom Tromey To: Mark Kettenis Cc: gdb-patches@sourceware.org Subject: Re: [RFC, PATCH] YACC parsers References: <201112171937.pBHJbDhq010089@glazunov.sibelius.xs4all.nl> Date: Mon, 19 Dec 2011 15:15:00 -0000 In-Reply-To: <201112171937.pBHJbDhq010089@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Sat, 17 Dec 2011 20:37:14 +0100 (CET)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-12/txt/msg00638.txt.bz2 >>>>> "Mark" == Mark Kettenis writes: Mark> It may not be impossible to "fix" the OpenBSD yacc(4) here, but given Mark> the fact that it supports the -p option to add a prefix to all the Mark> relevant symbols that would be somewhat silly. Unfortunately, Mark> changing the build infrastructure to use yacc -p isn't exactly Mark> trivial. Mark> Opinions? What is hard about using yacc -p? I wouldn't mind getting rid of these hacks and requiring a -p-capable yacc. Or even requiring Bison; I think this would only be needed by gdb developers anyhow. Tom