Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings

On 4/24/05, [e-mail] <[e-mail]> wrote:
> Hi,
> 
> At Wed, 20 Apr 2005 23:37:37 +0900,
> Erik Huelsmann wrote in [ruby-core:04747]:
> > Oh, but you mean that Ruby should switch to using typedef and somehow
> > should detect that the type already exists? I'm not aware of the
> > possibility to do so, but if the compiler only issues a warning, that
> > would be fine by me.
> 
> Such redefinition is disallowed.
> 
> > I was also thinking that maybe both sides should use (in the unix
> > version of their systems) ruby_pid_t and apr_pid_t. Then, those can be
> > defined to pid_t on Unix systems and to int on Win32. Also, it would
> > prevent namespace conflicts...
> 
> Ruby is just using AC_TYPE_UID_T.  So, using typedef for them,
> like as apr.h, means conflicts to all of autoconfiscated
> softwares.  I think apr.h should #undef before typedef.

Ah, but it only does that on Windows, not on POSIX platforms. On POSIX
platforms, it uses what's there. Just like Ruby. I don't think it's a
solution for ruby to require that APR uses #undef before the typedef:
that would require a change to *all* software with which Ruby is meant
to be compiled on windows. Not a pretty solution.

I think neither APR nor Ruby should be 'messing' with types defined by
POSIX. I'm preparing a patch for APR to stop doing this.

I intend to provide a patch for Ruby which defines a rb_pid_t (and
friends) for all platforms. (If you want it to be differently named:
that's fine ofcourse.) On windows it will be defined to int, on other
platforms, it will be defined to AC_TYPE_PID_T.

Is that the right course of action to take?

BTW: The fact that public CVS has been shut down does not really help
getting to the sources :-)  What's the ETA for CVS to come up again?


Bye,


Erik.

PS: Have you considered switching to Subversion? It has fewer issues
than CVS :-)