|
From: Werner L. <wl...@gn...> - 2014-10-06 15:46:44
|
>> If you build with msys, the default prefix `/usr/local' definitely
>> points into msys.
>
> I never build on Windows without an explicit --prefix argument. It
> is not useful to do otherwise, as the result will be at best
> unreliable and at worst simply won't work. /usr/local is not an
> absolute file name on Windows, and even if it happens to exist on
> some drive, it will not be what you intended.
Now I know, thanks. It's not trivial to grasp all those intricate
details of the differences between msys and MinGW.
>> 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...
>
> Not if the executable is "relocatable", i.e. can look for the files
> relative to its own location.
Indeed. However, I guess that by default bison 3.0.2 doesn't do
this...
> Ah, that rings a bell. Do you have a line in your config.h saying
> something like
>
> #define M4 "/d/foo/bar/m4"
>
> [...]
I will be able to check that in two days.
> I presumed that you are working with a debugger to solve these
> issues, because then you'd see immediately the reason for the above
> problem.
Maybe next time...
> There are a couple of other issues with Bison 3.0.2 on Windows (yes,
> I built it just today, so now I know ;-). If you still want to
> build your own, I can send you the patches.
Please do so. It sounds like you've solved the problem; this would
then simplify everything :-)
Werner
|