Re: [Mingw-users] bison 3.0.2 and m4sugar.m4

[Werner L. <wl...@gn...>]

>> Essentially you say that for *all* packages I should set `--prefix'
>> to a non-msys-mounted directory, right?
>
> That too, but it's a separate issue.  Bison should work regardless of
> its configure-time --prefix setting.

How shall this work out of the box?  If you build with msys, the
default prefix `/usr/local' definitely points into msys.  If I move
bison out of the tree, the m4 files in the `/usr/local/' hierarchy are
no longer found...  So I have to set the undocumented
`BISON_PKGDATADIR' environment variable to circumvent this...

> Do you have m4.exe installed, and is that m4.exe a MinGW program or
> an MSYS program?  It should be a MinGW program.

Now I have two m4.exe programs.  The first comes with msys and fails
for my non-msys bison.  Then I've rebuilt m4.exe with the standard
`./configure; make; make install' incantation into a prefix outside of
msys (the same as with my new bison program for convenience).  This
makes it a MinGW program, right?  Finally, I've rebuilt bison,
assuring that bison's `configure' program really uses the newly built
m4 executable.  After adjusting PATH to make the new bison and m4 be
found first, it still fails in both the `cmd' and `msys' shell.

> If you need an MSYS bison, and there's no newer version on the MinGW
> download site, you need to build it.  I never build an MSYS program,
> but AFAIU you will need an MSYS development environment, available
> from the download site.

Sigh.  I guess I'm out of patience now.  The whole issue has cost me
more than two days, with zero results.  Given that MinGW64 comes with
a recent bison version, I will try this route now.

> Btw, what exactly is wrong with the version of MSYS bison 2.4.2 that
> makes it "too old" for your purposes?

I need version 2.5 or newer because I use the very convenient feature
of named references.


    Werner