For what it is worth there is also an apparent problem with
perlivp seen on both Solaris 2.8 and VMS 7.3. The problem
is worse on VMS where ExtUtils::Installed seems to have
at least one bug in it.
I'll also try to post more as I get tuit.
Peter Prymmer
"Craig A. Berry"
<craigberry@mac. To: [EMAIL PROTECTED]
com> cc:
08/02/2002 06:15 Subject: extension building broken in
5.8.0
PM
There is a general problem with building extensions *against an
installed Perl* on VMS with 5.8.0. Basically there are several
include files missing for assorted reasons. I have a fix in the
works, but given the way things go it probably won't appear in a
production release for a year or more. I'll be sure to post the fix
here, but in the meantime there are a couple of workarounds:
1.) Build your extensions against the Perl build directory, not
against the installed Perl. That will pick up all the include files.
You can do this by defining PERL_ROOT to point to the build directory
while you build the extension and then pointing it back to the
installed Perl to test and install it.
OR
2.) Copy the include files from the Perl build directory into your
installed Perl like so (as Paul Simons did for the Clone extension):
$ copy fakethr.h perl_root:[lib.vms_ARCH.5_8_0.core]
$ copy perlsfio.h perl_root:[lib.vms_ARCH.5_8_0.core]
where ARCH is either vax or axp depending on your architecture. If
you have a threaded build, you'll need to do the same thing with
reentr.h. Be sure to check file ownership and protections after doing so.
--
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
