http://www.winehq.com/Docs/wine-devel/testing-windows.shtml says:
Run msvcmaker to generate Visual C++ project files for the tests. ...
$ ./tools/winapi/msvcmaker --no-wine
I did that in my cvs wine directory, and all I got was .: searching for /.spec$/ .: searching for /^Makefile.in$/ <internal>: options.pm: member W0B5 does not exists
Um, did I do something wrong? Or is there a bug in msvcmaker?
There is nothing wrong with msvcmaker on my computer.
The error above is very strange, nothing reasonable in the script that I think of can have caused it.
I'm on Red Hat 8.0, btw.
It can be some sort of name collision when the Perl modules are imported.
My guess is that one (or more) of the imported modules happens to depend on a module named "options" which causes a name collision.
Patrik Stridvall wrote:
http://www.winehq.com/Docs/wine-devel/testing-windows.shtml says:
Run msvcmaker to generate Visual C++ project files for the tests. ...
$ ./tools/winapi/msvcmaker --no-wine
I did that in my cvs wine directory, and all I got was .: searching for /.spec$/ .: searching for /^Makefile.in$/ <internal>: options.pm: member W0B5 does not exists
Aha. Caught by internationalization. The workaround is
LANG=C export LANG ./tools/winapi/msvcmaker --no-wine
I guess the FAQ needs updating... or the tool needs fixing...
I suspect the easiest "fix" would be to wrap msvcmaker with LANG=C export LANG
BTW, this is only one of many things that breaks when non-C locales are used. Others I know of: * 'man' when displayed in xterm or konsole (see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75089 where Red Hat says they will not support xterm, and also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75642) * all text processing utils are 10x or more slower (makes it hard to grep through large log files) * sort gives nonintuitive results (not a bug, just very suprising)
- Dan
-
Dan Kegel -
Patrik Stridvall