Mark Berryman wrote:
!If the files are supposed to be in the kit, then they are missing. They
!are not in the Tar file. I unpacked the Tar file on a Unix system and
!got the same result.
!
!Observe the following:
!
!> pwd
!/export/home/berryman/perl-5.8.1-RC3/ext/Encode
!> grep -i byte MANIFEST
!Byte/Byte.pm Encode extension
!Byte/Makefile.PL Encode extension
!> ls Byte
!Byte.pm Makefile.PL
Yes - my mistake. Files like byte_t.h do not ship
with the perl kit. Rather they are built during
the "perl Makefile.PL" step that occurs for the Encode
extension at mmk time. (strictly speaking it looks
like it occurs for the "perl Makefile.PL" step done
for [.ext.encode.byte]).
!Also:
!tar -tf perl-5_8_1-rc3.tar | grep -i _t.h
!
!returns no results.
!
!I fetched my kit from:
!http://www.cpan.org/authors/id/J/JH/JHI/perl-5.8.1-RC3.tar.gz
How does the build fair on Unix for you? I got RC3 to build on VMS
using DEC C S6.5-002, VMS 7.3-1, on an ODS-2 volume. I obtained
three test failures during a run of "mmk test".
What happens if you temporarily define your perl_root
to point to the build directory then you issue:
set def [.ext.encode.byte]
perl Makefile.PL
mmk
Are there any helpful error messages generated?
Peter Prymmer
