Gianni Mariani writes:
> > The 7.4 version of plperl.c (with some error handling API calls
> > commented out) compiles fine in the 7.3.4 tree.
> > (Same machine - same install of perl !) Points to using some
> > alternate perl API probably by macro collision ?
>
> /* Define to 1 to build client l
Quoting Gianni Mariani <[EMAIL PROTECTED]>:
> Keith C. Perry wrote:
>
> >I had this same issue as well but now I'm *slightly* concerned since most of
> my
> >code is perl. How soon would issue be reviewed? (not that I'm NOT going to
> use
> >your patch for right now).
> >
>
> I suspect that thi
Keith C. Perry wrote:
I had this same issue as well but now I'm *slightly* concerned since most of my
code is perl. How soon would issue be reviewed? (not that I'm NOT going to use
your patch for right now).
I suspect that this is only an issue when you use
"--enable-thread-safety" which accordi
Quoting "Keith C. Perry" <[EMAIL PROTECTED]>:
> Quoting Gianni Mariani <[EMAIL PROTECTED]>:
>
> > Gianni Mariani wrote:
> >
> > >
> > > Before I go deep into this - does anyone have the quick fix for this ?
> > >
> > > Some facts - the 7.3.4 version of plperl.c has the same errors in the
> > >
Quoting Gianni Mariani <[EMAIL PROTECTED]>:
> Gianni Mariani wrote:
>
> >
> > Before I go deep into this - does anyone have the quick fix for this ?
> >
> > Some facts - the 7.3.4 version of plperl.c has the same errors in the
> > 7.4 tree.
> > The 7.4 version of plperl.c (with some error handli
