Hi,

Do following problems also appear on Ruby 1.9.0?  I don't modify these
part from 1.9.0.

Giaour wrote:
> Hello,
> 
> I was trying to build yarv CVS snapshot on windows and ran into
> following problem:
>   For some reason yarv has "getenv=rb_w32_getenv" in its .def file.
> Obviously it conflicts with getenv from runtime (I used libcmt.lib
> runtime) during linking. Commenting it out works, but I don't know if
> it right way to fix it :)
> I understand why yarv has *nix calls there like geteuid, getgid, etc..
> But having windows ones either (getc, getenv, getcwd) is like asking
> for such link problems.
> 
> And while I'm here, I'd like to complain about win32.h:
> We have a bunch of macros like '#define listen(s, b) rb_w32_listen(s, b)'
> there. I already had problems with them in ruby-1.8.5 and hoped it is
> fixed in yarv... problems like
> #include <ruby.h>
> struct Person {
> ...
>    void listen(Person &who, Location &where);
> }
> This listen() ofcourse gets replaced with rb_w32_listen which breaks
> everything. If you want all listen() calls inside yarv code to be
> actually rb_w32_listen calls on windows, there must be better way to
> do it.
> 
> Last issue I ran into is calling conventions. Yarv compiles fine with
> cdecl as default, but fails if default is stdcall. This can be easily
> fixed by specifying calling convention explicitly where needed (there
> are not so many places where it has to be changed).
> 


-- 
// SASADA Koichi at atdot dot net



--
ML: yarv-dev-en quickml.atdot.net
Info: http://www.atdot.net/~ko1/quickml