fatal error: invalid @ in skeleton: @output m4_fst

[Philip Ashmore]

Binary package hint: bison

# lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

bison verson: 2.4.1

Yes I know that writing your own bison skeleton files is officially unsupported, but I think the approach I've taken is worth the effort.

Regardless of whether or not it's supported, I believe this bug indicates a problem in bison 2.4.1 that isn't present in bison 2.3.

Rather than spend a thousand words to help you recreate the problem, I've created a project in SourceForge that will save time.

    http://sourceforge.net/projects/cxxparse/
To build this you will also need
    http://sourceforge.net/projects/v3c/
as well as bison, flex and the packages detailed in v3c/README.

You can either download the .tar.gz files or clone their GIT repositories.

I (and now you) can build the Debian packages for v3c and then cxxparse by unpacking them, entering the same directory as their respective README files and running
    make debian
You need to install the Debian / Ubuntu packages for v3c first by
    cd build && sudo dpkg -i *.deb
Once done you are in a position to build the cxxparse package.

The skeleton I've written generates another file containing a class that contains the lex token enumeration and the example in
cxxparse/flexx/tests shows how this is used as a base class by the scanner - all very c++ and neat.

Except it doesn't work on Ubuntu - hence this bug report.
I'm pretty sure that it's because Ubuntu supplies bison 2.4.1 whereas Debian comes with bison 2.3.

Ideally you could take my skeleton as "inspiration" for another bison skeleton, but if not then helping me solve this problem would be good too.

What is expected to happen:
    built debian/ubuntu packages in the cxxparse build directory
What happened instead:
    ../../../../v3c/flexx/tests/calc.ypp: fatal error: invalid @ in skeleton: @output m4_fst

[Philip Ashmore (contact-philipashmore)]

It turns out that I had to rewrite the bison skeleton for bison 2.4.1.

I updated my sourceforge project to handle bison 2.4.1 specially.

Please consider this bug as closed - RTFM or "read the frigging documentation"!