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

[Akim Demaille]

>>>>> "Mike" == Mike Castle <address@hidden> writes:

Mike> In article <address@hidden>,
Mike> Akim Demaille  <address@hidden> wrote:

>> Thanks, this is a known issue.  For my own education, could tell me
>> why you'd need this option?

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

Wow.

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

It seems to be quite a dangerous feature :(

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

Well, now you have a working --no-line :).