[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bison, G++, and M4

From: Paul Pluzhnikov
Subject: Re: Bison, G++, and M4
Date: Wed, 03 Oct 2007 16:41:14 -0700
User-agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux) writes:

> Hullo. I was re-directed here from comp.lang.c++

This is probably not the right place either, but I'll try to help.

> I think what is *supposed* to happen is that somehow, somewhere, the
> m4 processor is  supposed to run,
> replacing these macros with standard code, which is then properly
> compiled.  I already know it is  not being called by g++.  Where,
> then?

g++ does not, never did, and never will, call m4.
And bison doesn't really have anything to do with the problem either.

The *author* of your program most likely screwed up, and instead
of packaging source code after preprocessing it with m4, he packaged
it with m4 macros still un-expanded.

Alternatively, the Makefile that came with the source is broken,
and doesn't run m4 before compiling the source, even though it was
supposed to.

> For some reason m4 is not replacing the macro calls.

Likely because m4 is not being invoked. 

> Suggestions? 

Either contact the author of your package for advice, or figure
out the Makefile and fix it, or run m4 by hand to generate compilable

In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]