On Mon, Oct 29, 2012 at 11:59:50AM -0700, Chuan-kai Lin wrote:
Bill,
bison 2.6.4 is out at http://ftp.gnu.org/gnu/bison/ - can you check if
the new version fixes this bug?
I do not think there is any expectation that bison 2.6.4 fix this bug.
On the other hand, Felipe Sateler has raised the
severity 689700 normal
clone 689700 -1
retitle -1 Downgrade to version 2.4 until wheezy is released
severity -1 serious
thanks
On Wed, Oct 31, 2012 at 8:06 AM, Bill Allombert
bill.allomb...@math.u-bordeaux1.fr wrote:
On Mon, Oct 29, 2012 at 11:59:50AM -0700, Chuan-kai Lin wrote:
Bill,
Processing commands for cont...@bugs.debian.org:
severity 689700 normal
Bug #689700 [bison] bison: generate incompatible header file
Severity set to 'normal' from 'serious'
clone 689700 -1
Bug #689700 [bison] bison: generate incompatible header file
Bug 689700 cloned as bug 691928
retitle -1
Bill,
bison 2.6.4 is out at http://ftp.gnu.org/gnu/bison/ - can you check if
the new version fixes this bug?
Thanks,
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi,
Maybe the following proposal went unnoticed.
Le 19 oct. 2012 à 10:43, Akim Demaille a écrit :
Nevertheless (I don't know Debian's schedule), there are a
few bugs in 2.6.2 that have been fixed, and are scheduled
to be released in 2.7 (say a couple of weeks). Would Debian
folks like a
On Sun, Oct 21, 2012 at 9:24 AM, Akim Demaille a...@lrde.epita.fr wrote:
Hi,
Maybe the following proposal went unnoticed.
Le 19 oct. 2012 à 10:43, Akim Demaille a écrit :
Nevertheless (I don't know Debian's schedule), there are a
few bugs in 2.6.2 that have been fixed, and are scheduled
Hi all!
Le 18 oct. 2012 à 17:53, Bill Allombert a écrit :
On Thu, Oct 18, 2012 at 02:15:38PM +0200, Akim Demaille wrote:
Hi Bill,
(and more to the point, Debian 'testing' includes bison 2.5 and
Debian 'unstable' includes bison 2.6 and some software in
'testing' does not build on
Hi Frank,
Le 18 oct. 2012 à 18:52, Frank Heckenbach a écrit :
We do compile our Bison output with g++ (yes, we should probably use
the C++ skeleton, but we haven't gotten around to it yet),
I'd be happy to give a hand, and get some feedback
about it.
and we
don't use extern C -- in fact we
Akim Demaille wrote:
Indeed, if you want both to be in the same namespace, %define api.prefix
should do what you want.
Note that the C++ output supports %define namespace, in
which the generated code is put.
Thanks, seems like we have several viable options here. (Though I'd
have to check
Processing commands for cont...@bugs.debian.org:
forwarded 689700
http://lists.gnu.org/archive/html/bug-bison/2012-10/msg9.html
Bug #689700 [bison] bison: generate incompatible header file
Set Bug forwarded-to-address to
'http://lists.gnu.org/archive/html/bug-bison/2012-10/msg9.html
Sorry for the late reply, your mail was eaten by my spam filter.
On Sun, Oct 14, 2012 at 9:09 AM, Bill Allombert
bill.allomb...@math.u-bordeaux1.fr wrote:
On Sat, Oct 13, 2012 at 05:18:48PM -0700, Chuan-kai Lin wrote:
On Sat, Oct 13, 2012 at 3:35 PM, Felipe Sateler fsate...@debian.org wrote:
On Thu, Oct 18, 2012 at 02:15:38PM +0200, Akim Demaille wrote:
Hi Bill,
(and more to the point, Debian 'testing' includes bison 2.5 and
Debian 'unstable' includes bison 2.6 and some software in
'testing' does not build on 'unstable', but this is something for
the Debian maintainer to
PS:
Bill Allombert wrote:
When you allow to compile C files with a C++ compiler, it is customary to use
extern C, otherwise you ABI depend on the compiler.
It probably does, but for us that's not relevant since we compile
everything with GCC anyway.
Frank
--
To UNSUBSCRIBE, email to
Bill Allombert wrote:
A way to fix the problem could be to add
#ifdef __cplusplus
extern C {
#endif
...
#ifdef __cplusplus
}
#endif
in the generated parse.tab.h.
This is not correct for people who do not want this guy to be
in extern C.
I agree, but I
On Thu, Oct 18, 2012 at 06:52:41PM +0200, Frank Heckenbach wrote:
Bill Allombert wrote:
We do compile our Bison output with g++ (yes, we should probably use
the C++ skeleton, but we haven't gotten around to it yet), and we
don't use extern C -- in fact we use two different parsers in one
Bill Allombert wrote:
On Thu, Oct 18, 2012 at 06:52:41PM +0200, Frank Heckenbach wrote:
Bill Allombert wrote:
We do compile our Bison output with g++ (yes, we should probably use
the C++ skeleton, but we haven't gotten around to it yet), and we
don't use extern C -- in fact we use two
On Wed, Oct 17, 2012 at 11:00:49AM -0700, Chuan-kai Lin wrote:
Hi,
I am forwarding this bug report by Bill Allombert from the Debian bug
tracking system (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689700).
Here is Bill's report:
Dear bison developers,
I realise my report
On Sat, Oct 13, 2012 at 05:18:48PM -0700, Chuan-kai Lin wrote:
On Sat, Oct 13, 2012 at 3:35 PM, Felipe Sateler fsate...@debian.org wrote:
This causes unrelated packages to break. Please revert this change
until wheezy is released, since it makes fixing bugs in testing harder
than necessary
On Sat, Oct 13, 2012 at 9:18 PM, Chuan-kai Lin chk...@gmail.com wrote:
On Sat, Oct 13, 2012 at 3:35 PM, Felipe Sateler fsate...@debian.org wrote:
This causes unrelated packages to break. Please revert this change
until wheezy is released, since it makes fixing bugs in testing harder
than
On Sat, Oct 13, 2012 at 3:35 PM, Felipe Sateler fsate...@debian.org wrote:
This causes unrelated packages to break. Please revert this change
until wheezy is released, since it makes fixing bugs in testing harder
than necessary for pacakges build-depending on bison.
Do you happen to know what
20 matches
Mail list logo
