From MAILER-DAEMON Fri Jan 06 05:23:55 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cPRgh-0003sX-GB
	for mharc-bug-bison@gnu.org; Fri, 06 Jan 2017 05:23:55 -0500
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36363)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <brandon@gnu.org>) id 1cPRge-0003q5-NS
	for bug-bison@gnu.org; Fri, 06 Jan 2017 05:23:53 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <brandon@gnu.org>) id 1cPRgd-0006Hz-VB
	for bug-bison@gnu.org; Fri, 06 Jan 2017 05:23:52 -0500
Received: from fencepost.gnu.org ([2001:4830:134:3::e]:46261)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <brandon@gnu.org>)
	id 1cPRgd-0006Hv-SP; Fri, 06 Jan 2017 05:23:51 -0500
Received: from brandon by fencepost.gnu.org with local (Exim 4.82)
	(envelope-from <brandon@gnu.org>)
	id 1cPRgd-0007vU-K3; Fri, 06 Jan 2017 05:23:51 -0500
From: Brandon Invergo <brandon@gnu.org>
To: bug-bison@gnu.org, help-bison@gnu.org
Subject: GNU Bison is in need of a co-maintainer
Organization: GNU
Date: Fri, 06 Jan 2017 05:23:51 -0500
Message-ID: <yudwpe8trk8.fsf@fencepost.gnu.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2001:4830:134:3::e
X-BeenThere: bug-bison@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Bug reports for Bison, the GNU parser generator" <bug-bison.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-bison/>
List-Post: <mailto:bug-bison@gnu.org>
List-Help: <mailto:bug-bison-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jan 2017 10:23:53 -0000

Hi everyone,

GNU Bison is in need of a new co-maintainer.  If you're interested,
please take a look at this general information about GNU packages and
being a GNU maintainer, and then email maintainers@gnu.org with a bit
about your background and particular interest in the project:

https://www.gnu.org/help/evaluation.html#whatmeans

Thanks,
Brandon


From MAILER-DAEMON Thu Jan 12 15:55:27 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cRmP9-00045W-SZ
	for mharc-bug-bison@gnu.org; Thu, 12 Jan 2017 15:55:27 -0500
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55049)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gabocze@gmail.com>) id 1cRmP7-00045G-0Z
	for bug-bison@gnu.org; Thu, 12 Jan 2017 15:55:26 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gabocze@gmail.com>) id 1cRmP6-0004sp-4B
	for bug-bison@gnu.org; Thu, 12 Jan 2017 15:55:25 -0500
Received: from mail-oi0-x234.google.com ([2607:f8b0:4003:c06::234]:34119)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gabocze@gmail.com>) id 1cRmP5-0004se-UZ
	for bug-bison@gnu.org; Thu, 12 Jan 2017 15:55:24 -0500
Received: by mail-oi0-x234.google.com with SMTP id m124so948586oif.1
	for <bug-bison@gnu.org>; Thu, 12 Jan 2017 12:55:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:from:date:message-id:subject:to;
	bh=otFo3iXuTDMDON8NsOQQ8yuB92kc5+BCIfnK8azZAhA=;
	b=FefkW2zxBWNjDqowfaXmAUWUnrAdbrweLMJVCdsu81UmITwt9cZQT2ngSvwrWdaBov
	qoksqQGnXxVYmVyV5ORG/5ww4YKwxqicxJMV3GqdL3OCOZVoKP6nASppwnbeUaoxSlYG
	b2Ka702bDx8LxpPlJMuBA5mu2/15aifYqepx5xE23K1uG9viSW/tVPSefECiY5DoBNwy
	hvtvP0yuf0b0940jf64vAaCSnrkCe8yUEZjuc7IYlcGgjBrZmEqWEYcPEUl3yVJ6G9Sq
	4agx2pj9mS/6P1z3ZgB2AxV9EfmjYAAFLJLT5OADGsD54lejIoAV6AawXOW2jiJrPP0c
	eewA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
	bh=otFo3iXuTDMDON8NsOQQ8yuB92kc5+BCIfnK8azZAhA=;
	b=dLldZAaZIrklADRZL+Nvr8f8F51dCA27tQB0LPBpA33wfwaf/TfSFXMhOVv3pi4m0L
	opN3/Drd4YwMy1CKICW3SySTd9pwmmnSvK2IH1maZa7EAcslqecj9qZPA6AsZLcqxa+B
	pOsAW4CJ9geMiLhG4Lb45GLwXfteAjWQT4HuQnwXRbotg+MFdF+RyPuCkpDxqCRN9dSb
	e4Utypc+Y2dNphISa4hHy9pCt8RvKHgo5TXn8/tT2U3dFtbjno9a7dFMvGYTiyvu7/i9
	Bqhx0Oh1T0nqLJlyC2DMMCmWKbjCmP+VzkoeHDOmILDMfiX12/z6Db0gX10DAkKKjFC3
	sB6w==
X-Gm-Message-State: AIkVDXKwIuTzw1w8EncqsyzfJvgIQ9McKeSpO5Waa9KmNOCBGQ+F4lkBcRa7zaMFzVwZbrAlRm/qfo6Lf59/Yw==
X-Received: by 10.202.197.135 with SMTP id v129mr7442902oif.131.1484254522737; 
	Thu, 12 Jan 2017 12:55:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.11.171 with HTTP; Thu, 12 Jan 2017 12:55:22 -0800 (PST)
From: Gabriel Czernikier <gabocze@gmail.com>
Date: Thu, 12 Jan 2017 17:55:22 -0300
Message-ID: <CAFjAi4oop7EeiRj4aus_irxuc2OOovpJYLYwvx7coKROjVV58A@mail.gmail.com>
Subject: Bug in documentation for 3.0.4
To: bug-bison@gnu.org
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2607:f8b0:4003:c06::234
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
X-BeenThere: bug-bison@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Bug reports for Bison, the GNU parser generator" <bug-bison.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-bison/>
List-Post: <mailto:bug-bison@gnu.org>
List-Help: <mailto:bug-bison-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2017 20:55:26 -0000

Hello,

I find the section 3.4.8.2 Mid-Rule Action Translation being a bit
confusing, for what I raise this bug report.

As I understand per the first paragraph, the goal of this section is to
show how mid-rule translation works, and the output of one or more Bison
reports revealing the structural grammar changes due to that translation.

The next lines of text, give examples of grammars containing mid-rules and
the translations that take place on them, which ultimately works for the
sake of the lesson taught by this section.

The last example, by its own side, is intended to show tne outcomes of a
mid-rule that refers to an unused $$, and a final (last component) rule
that refer to a mid-rule without $$ asingment. Although, this goal is well
achieved, a reader could get confused expecting the output reveal the
translations about which were taken up in prior paragraphs.

The documentation should give one example that shows how the report of
Bison's output features alterations in the actual grammar. Or else, it
should make an statement that both given cases, the one with the grammar
translations and the one with the Bison invocation, are unrelated to each
other.

Regards,
Gabriel Czernikier

From MAILER-DAEMON Mon Jan 16 14:36:04 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cTD4W-0006Ea-MG
	for mharc-bug-bison@gnu.org; Mon, 16 Jan 2017 14:36:04 -0500
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59787)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gabocze@gmail.com>) id 1cTD4T-0006Ca-Nw
	for bug-bison@gnu.org; Mon, 16 Jan 2017 14:36:03 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gabocze@gmail.com>) id 1cTD4S-0003M3-7h
	for bug-bison@gnu.org; Mon, 16 Jan 2017 14:36:01 -0500
Received: from mail-oi0-x233.google.com ([2607:f8b0:4003:c06::233]:33773)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <gabocze@gmail.com>) id 1cTD4S-0003LI-1c
	for bug-bison@gnu.org; Mon, 16 Jan 2017 14:36:00 -0500
Received: by mail-oi0-x233.google.com with SMTP id w204so108050530oiw.0
	for <bug-bison@gnu.org>; Mon, 16 Jan 2017 11:35:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to; 
	bh=A1tY0fkN2CPkOfMa2uyfoL0+wGxVlgLbLey9rcct8OY=;
	b=i3TMXbcCyVjjDyv7GxhDFVNpAXuvxLsEYOq1+hz5VhCHuVJUjMi4ed+zlm2VDp+yUr
	cYc1THT9JLIUX3Hry8Cz/uixQoOldn9CPOg8jTpauACR7/YeNMi0CQwAXkltCK55yLJR
	V/HB9VsQM5JawtcbBj9AizGyqw+I0Ik+ITcltAtrpXR+92RA6o54Mc+FG1o4+beey5KV
	uFHiGEKew16zIq5tugmIhpxOHcYFImrfu1+qqxvrbB0+1M1IEAGR4nV2VARJ2diOJ5fP
	M/n9RE6XN0i4UnbhzgNFy9FDZCqOBp/pIjC45Q2G9VaJiUWePff0qNGrs4qmR0eoNzKs
	JmvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=A1tY0fkN2CPkOfMa2uyfoL0+wGxVlgLbLey9rcct8OY=;
	b=a5W1ieEKvMrMCQVx5W/fc1ajnwQSnmxhv0S8Gl+FW8RwXEYGgQrZERcZ+YiSdZsQ/J
	8FEekYtVMcVkxHQyDAWzHHB1LJnd2g6vTOLgT+d24F6dtb2GAzNscyf5O9w1ynnfuvmS
	yooKMj2BEPbFCS6AGjDhkzlmVN1ChsW5EXy+wJ5uWqWZpfK4STNSl5hX4HVRDvxdSjxC
	leSyjmPq1YqIj1k3FkEvVPpEGHc2bAhN3dfxmZW0qygB4AHZdQQzZFCoS1r0GxqTwvm2
	qDShjNpk66LPdJiJJDsIbJPX15OD+MF4l3dHGrBMhZoJxXkDvkiOVNpoEr0rWdDwEpfb
	T5lQ==
X-Gm-Message-State: AIkVDXKChYsUSLY8ZYRS/xnZ0c/OXKb+n3A9bDdSgg0vPiL36SpnuwHOFI5QG75doHZOnPJQS6NtE0CeBHZZNA==
X-Received: by 10.202.218.134 with SMTP id r128mr1536571oig.2.1484595357615;
	Mon, 16 Jan 2017 11:35:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.57.161 with HTTP; Mon, 16 Jan 2017 11:35:56 -0800 (PST)
In-Reply-To: <CAFjAi4oop7EeiRj4aus_irxuc2OOovpJYLYwvx7coKROjVV58A@mail.gmail.com>
References: <CAFjAi4oop7EeiRj4aus_irxuc2OOovpJYLYwvx7coKROjVV58A@mail.gmail.com>
From: Gabriel Czernikier <gabocze@gmail.com>
Date: Mon, 16 Jan 2017 16:35:56 -0300
Message-ID: <CAFjAi4pqZNmRoxTNMwmCj+p1WAObiZ=OcVN1etsr2gtEZFB9HA@mail.gmail.com>
Subject: Re: Bug in documentation for 3.0.4
To: bug-bison@gnu.org
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2607:f8b0:4003:c06::233
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
X-BeenThere: bug-bison@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Bug reports for Bison, the GNU parser generator" <bug-bison.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-bison/>
List-Post: <mailto:bug-bison@gnu.org>
List-Help: <mailto:bug-bison-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jan 2017 19:36:03 -0000

I would give me a take to explain it better.

The introduction of the section 3.4.8.2, "Mid-Rule Action Translation"
makes it seeming that a subject will be addressed along the section about
how Bison's reports can reveal that the grammar was changed to a different
form, after applying mid-rules processing. Thru the end of the section, it
doesn't happen.

It wouldn't be a true bug, if other sections of the manual took up to
address the subject. The section "8.1 Understanding your parser", is
probably the major candidate to do this job, since the introduction of the
secction in question (3.4.8.2) points to it as the place to find more
information. If section 8.1 already does it, that could mean the end of
this bug. If not, it could mean the need of putting a better reference in
the introduction (which doesn't mean to remove the current reference to
8.1).

Anyway, the introduction states that Bison's reports reveal the
translations in the grammar when any of them has taken place, but it
doesn't specify which of all the reports are reached by this statement. By
the end of the section, there is kind of and example of an invocation to
Bison and its return messages when run for a grammar having mid-rules hence
owning the conditions to be translated. Though not its major sake, this
example is an opportunity to make a point on the subject. Because it
doesn't care to do so, it can left the reader in a feeling of hesitation,
perhaps wondering any of the following:
- Does the report contained in this example falls out of the category of
Bison's reports that reveal translations in grammars?
- Does this example purposely simplifies things by means of ommiting the
translations in the grammar that would be revealed in real life?
- Is it all about an error in the manual?

After all, and to sum things up, what we have is:
- An introduction, making a sort of assertion on grammar translations and
reports revealing them.
- A section in which this introduction is found, not careing to show an
example of that.
- An example, by the end of the section that, while playing for a different
purpose, makes doubt turn out if the it has to be reformulated in how the
messages are reported to be consistent with "revealing the translations".
- A reference to other section that, in the case of expanding the subject
with examples and/or specifications, results in leaving the first section
being not self-contained. Not a big problem, would be my personal opinion.

Regards,
Gabriel Czernikier


On Thu, Jan 12, 2017 at 5:55 PM, Gabriel Czernikier <gabocze@gmail.com>
wrote:

> Hello,
>
> I find the section 3.4.8.2 Mid-Rule Action Translation being a bit
> confusing, for what I raise this bug report.
>
> As I understand per the first paragraph, the goal of this section is to
> show how mid-rule translation works, and the output of one or more Bison
> reports revealing the structural grammar changes due to that translation.
>
> The next lines of text, give examples of grammars containing mid-rules and
> the translations that take place on them, which ultimately works for the
> sake of the lesson taught by this section.
>
> The last example, by its own side, is intended to show tne outcomes of a
> mid-rule that refers to an unused $$, and a final (last component) rule
> that refer to a mid-rule without $$ asingment. Although, this goal is well
> achieved, a reader could get confused expecting the output reveal the
> translations about which were taken up in prior paragraphs.
>
> The documentation should give one example that shows how the report of
> Bison's output features alterations in the actual grammar. Or else, it
> should make an statement that both given cases, the one with the grammar
> translations and the one with the Bison invocation, are unrelated to each
> other.
>
> Regards,
> Gabriel Czernikier
>
>

From MAILER-DAEMON Tue Jan 31 12:31:26 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cYcH8-0007AX-FZ
	for mharc-bug-bison@gnu.org; Tue, 31 Jan 2017 12:31:26 -0500
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56390)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ajstewart@anl.gov>) id 1cYbt5-0000Kp-DC
	for bug-bison@gnu.org; Tue, 31 Jan 2017 12:06:36 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ajstewart@anl.gov>) id 1cYbt0-0007nI-Dx
	for bug-bison@gnu.org; Tue, 31 Jan 2017 12:06:35 -0500
Received: from mailrelay.anl.gov ([130.202.101.22]:49022)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ajstewart@anl.gov>) id 1cYbt0-0007mq-6w
	for bug-bison@gnu.org; Tue, 31 Jan 2017 12:06:30 -0500
Received: from mailgateway.anl.gov (mailgateway.anl.gov [130.202.101.28])
	(using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mailrelay.anl.gov (Postfix) with ESMTPS id E468F200093
	for <bug-bison@gnu.org>; Tue, 31 Jan 2017 11:06:27 -0600 (CST)
X-IronPort-AV: E=Sophos;i="5.33,315,1477976400"; 
	d="scan'208,217";a="143284062"
Received: from nagurski.anl.gov ([146.137.81.22])
	by mailgateway.anl.gov with ESMTP/TLS/DHE-RSA-AES256-SHA;
	31 Jan 2017 11:04:42 -0600
Received: from PAYTON.anl.gov ([fe80::745c:c48e:11e8:4088]) by
	NAGURSKI.anl.gov ([2002:9289:5110::9289:5110]) with mapi id
	14.03.0266.001; Tue, 31 Jan 2017 11:04:42 -0600
From: "Stewart, Adam James" <ajstewart@anl.gov>
To: "bug-bison@gnu.org" <bug-bison@gnu.org>
Subject: Unable to build Bison with PGI compilers
Thread-Topic: Unable to build Bison with PGI compilers
Thread-Index: AdJ75BzmQLtIY12nQNa6dKe8TMZBaw==
Date: Tue, 31 Jan 2017 17:04:41 +0000
Message-ID: <9F5501637440B04B9DE4C86279C60B6E4A59749E@PAYTON.anl.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [146.137.81.42]
MIME-Version: 1.0
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 130.202.101.22
X-Mailman-Approved-At: Tue, 31 Jan 2017 12:31:24 -0500
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
X-BeenThere: bug-bison@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Bug reports for Bison, the GNU parser generator" <bug-bison.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-bison/>
List-Post: <mailto:bug-bison@gnu.org>
List-Help: <mailto:bug-bison-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2017 17:06:36 -0000

Hi,

I'm trying to install Bison 3.0.4 with PGI 16.5, but make crashes with the =
following error messages:

src/bison-InadequacyList.o: In function `xnmalloc':
/blues/gpfs/home/software/spack-0.10.0/var/spack/stage/bison-3.0.4-qofkgp3x=
fpikbq7oj7khyo6sh6mmmmgj/bison-3.0.4/lib/xalloc.h:108: multiple definition =
of `xnmalloc'
src/bison-AnnotationList.o:/blues/gpfs/home/software/spack-0.10.0/var/spack=
/stage/bison-3.0.4-qofkgp3xfpikbq7oj7khyo6sh6mmmmgj/bison-3.0.4/lib/xalloc.=
h:108: first defined here
src/bison-InadequacyList.o: In function `xnrealloc':
/blues/gpfs/home/software/spack-0.10.0/var/spack/stage/bison-3.0.4-qofkgp3x=
fpikbq7oj7khyo6sh6mmmmgj/bison-3.0.4/lib/xalloc.h:121: multiple definition =
of `xnrealloc'
src/bison-AnnotationList.o:/blues/gpfs/home/software/spack-0.10.0/var/spack=
/stage/bison-3.0.4-qofkgp3xfpikbq7oj7khyo6sh6mmmmgj/bison-3.0.4/lib/xalloc.=
h:121: first defined here
src/bison-InadequacyList.o: In function `xcharalloc':
/blues/gpfs/home/software/spack-0.10.0/var/spack/stage/bison-3.0.4-qofkgp3x=
fpikbq7oj7khyo6sh6mmmmgj/bison-3.0.4/lib/xalloc.h:220: multiple definition =
of `xcharalloc'

I can provide you with the entire build output if you want.

Adam J. Stewart
Assistant Systems Administrator
Laboratory Computing Resource Center
Computing, Environment and Life Sciences
Argonne National Laboratory

From MAILER-DAEMON Tue Jan 31 17:31:50 2017
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1cYgxq-0006nc-OL
	for mharc-bug-bison@gnu.org; Tue, 31 Jan 2017 17:31:50 -0500
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51694)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1cYgxo-0006hT-Hj
	for bug-bison@gnu.org; Tue, 31 Jan 2017 17:31:49 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1cYgxl-00054d-G3
	for bug-bison@gnu.org; Tue, 31 Jan 2017 17:31:48 -0500
Received: from zimbra.cs.ucla.edu ([131.179.128.68]:39606)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <eggert@cs.ucla.edu>) id 1cYgxl-00054P-AG
	for bug-bison@gnu.org; Tue, 31 Jan 2017 17:31:45 -0500
Received: from localhost (localhost [127.0.0.1])
	by zimbra.cs.ucla.edu (Postfix) with ESMTP id 64FCE1600E5;
	Tue, 31 Jan 2017 14:31:42 -0800 (PST)
Received: from zimbra.cs.ucla.edu ([127.0.0.1])
	by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032)
	with ESMTP id 4DXx3qqj5u2d; Tue, 31 Jan 2017 14:31:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by zimbra.cs.ucla.edu (Postfix) with ESMTP id 5DB281600EE;
	Tue, 31 Jan 2017 14:31:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu
Received: from zimbra.cs.ucla.edu ([127.0.0.1])
	by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026)
	with ESMTP id bMwYGIJezI5H; Tue, 31 Jan 2017 14:31:41 -0800 (PST)
Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200])
	by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 468E21600E5;
	Tue, 31 Jan 2017 14:31:41 -0800 (PST)
Subject: Re: Unable to build Bison with PGI compilers
To: "Stewart, Adam James" <ajstewart@anl.gov>,
	"bug-bison@gnu.org" <bug-bison@gnu.org>
References: <9F5501637440B04B9DE4C86279C60B6E4A59749E@PAYTON.anl.gov>
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
Message-ID: <d961590d-040a-6935-743a-964941ed4bc3@cs.ucla.edu>
Date: Tue, 31 Jan 2017 14:31:40 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
	Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <9F5501637440B04B9DE4C86279C60B6E4A59749E@PAYTON.anl.gov>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 131.179.128.68
X-BeenThere: bug-bison@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Bug reports for Bison, the GNU parser generator" <bug-bison.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-bison/>
List-Post: <mailto:bug-bison@gnu.org>
List-Help: <mailto:bug-bison-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bison>,
	<mailto:bug-bison-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2017 22:31:49 -0000

On 01/31/2017 09:04 AM, Stewart, Adam James wrote:
> Hi,
>
> I'm trying to install Bison 3.0.4 with PGI 16.5, but make crashes with the following error messages:
>
> src/bison-InadequacyList.o: In function `xnmalloc':
> /blues/gpfs/home/software/spack-0.10.0/var/spack/stage/bison-3.0.4-qofkgp3xfpikbq7oj7khyo6sh6mmmmgj/bison-3.0.4/lib/xalloc.h:108: multiple definition of `xnmalloc'

This is the same as the problem you reported against GNU M4 last March. 
PGI by default does not support the C99 'inline' keyword properly. A 
workaround was installed into Gnulib here:

http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=6c58857620e62135b0b748df436008eb3c3a23d6

This fix should appear in the next Bison version, whenever it comes out. 
In the meantime you can apply the Gnulib patch to your copy of Bison, 
and run 'make'; you'll need developer tools like Autoconf installed to 
do that.

I expect PGI's lack of support is inadvertent: that is, I suspect the 
PGI folks think that PGI supports C99 'extern inline', but the support 
is buggy. As a PGI user you might file a bug report with them, and you 
can point them at the Bison 3.0.4 source code as an example of the bug.


