Hi Patrick, Sorry I didn't respond the first time you tried to reach me...
ExtUtils::ParseXS isn't distributed with any version of perl yet, and I don't know of any vendors that bundle it either. Its main use is that it can be called from Module::Build, etc., without starting a subprocess, so it's much more portable to weird platforms. I took on this task because I needed it done, but unfortunately I have almost ZERO knowledge about how xsubpp should work. Maybe you could even give me a patch for it. ;-) The trick, though, is that I copied its code from bleadperl at one point, so I'm guessing that 5.8.x might also need to be fixed in the same way? -Ken > -----Original Message----- > From: Patrick LeBoutillier [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 04, 2004 8:47 AM > To: [EMAIL PROTECTED] > Subject: [somewhat OT] xsubpp problems > > > Hi all, > > This is slightly off topic but I'm thinking someone here can help. > > I'm having problems with a .xs file I just added to > Inline::Java. This .xs > file creates a .so that is meant to be loaded by JAVA and not by Perl. > Therfore is doesn't include your typical > > #include "EXTERN.h" > #include "perl.h" > #include "XSUB.h" > > and it doesn't call any Perl code whatsoever. It also doesn't have a > > MODULE ... PACKAGE ... PREFIX > > line in the .xs source. > > > My problem is that the "old" xsubpp doesn't care about this > and "compiles" > the .xs file properly. The "new" xsubpp, that is based on > ExtUtils::ParseXS, croaks saying: > > die "Didn't find a 'MODULE ... PACKAGE ... PREFIX' line\n" unless > defined $_; > > > So my real question is: How does one get the "new" xsubpp? > Do you have to manually install ExtUtils::ParseXS? > Are there some Perl distros that come already setup that way? I have > looked at 5.6.0, 5.6.1, 5.8.0, 5.8.2, 5.8.3 distros on RH > Linux and Win32 > and none had ExtUtils::ParseXS installed by default. > > I think I know how to fix the problem, I'm just trying to > determine how > much of my audience is affected by this issue. > > Thanks a lot, > > Patrick > >
