Re: Version 1.75-1 ignoring --no-lines flag

[Mike Castle]

In article <address@hidden>,
Akim Demaille  <address@hidden> wrote:
>Thanks, this is a known issue.  For my own education, could tell me
>why you'd need this option?

At least for gcc-3.0.2 and before, the #line statements would change
the includepaths.

So, consider a situation where: 1) The user was building outside of
srcdir and 2) using a gcc 3.0.2 or earlier.  The #line in the generated
source file, now in builddir, will cause the header file to be pulled
from srcdir, not builddir.  If the version of bison on the build machine
is sufficiently different from the version the maintainer used to create
the package, you can have significantly mis-matched headers.

I commented on this quite recently, asking for feedback on recommended
ways of handling this, but got no response.

mrc
-- 
     Mike Castle      address@hidden      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc