| Subject: | strawberry-perl-5.22.1.1-64bit.msi - Package installs requiring GCJ module installation fail due to missing header |
| Date: | Tue, 19 Jan 2016 17:35:45 +1100 |
| To: | bug-Perl-Dist-Strawberry [...] rt.cpan.org |
| From: | Helen OBoyle <hoboyle [...] gmail.com> |
Hi,
I'm trying to install the Import::Java module on a 64 bit version of
Strawberry Perl under Windows 7. This module has a dependency on the
GCJ::Cni module, and the GCJ::Cni module's installation is failing with the
error:
Building GCJ-Cni
Didn't find a 'MODULE ... PACKAGE ... PREFIX' line
RUSEKD/GCJ-Cni-0.03.tar.gz
C:\Strawberry64\perl\bin\perl.exe ./Build -- OK
Running Build test
gcc -c -s -O2 -DWIN32 -DWIN64 -DCONSERVATIVE -DPERL_TEXTMODE_SCRIPTS
-DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -fwrapv -fno-strict-aliasing
-mms-bitfields -x c++ -include gcj/cni.h -s -O2 "-DVERSION=\"0.03\""
"-DXS_VERSION=\"0.03\"" -I"C
:\STRAWB~1\perl\lib\CORE" -I"C:\STRAWB~1\c\include" -o "lib\GCJ\Cni.o"
"lib\GCJ\Cni.c"
cc1plus.exe: fatal error: gcj/cni.h: No such file or directory
compilation terminated.
error building xs.dll file from 'lib\GCJ\Cni.c' at
C:/Strawberry64/perl/lib/ExtUtils/CBuilder/Platform/Windows.pm line 129.
RUSEKD/GCJ-Cni-0.03.tar.gz
C:\Strawberry64\perl\bin\perl.exe ./Build test -- NOT OK
//hint// to see the cpan-testers results for installing this module, try:
reports RUSEKD/GCJ-Cni-0.03.tar.gz
Stopping: 'install' failed for 'GCJ::Cni'.
-------------------------------------------------
Show quoted text
> perl -v
This is perl 5, version 22, subversion 1 (v5.22.1) built for
MSWin32-x64-multi-thread
-------------------------------------------------
Show quoted text> gcc --version
gcc (x86_64-posix-sjlj, built by strawberryperl.com project) 4.9.2
I do not have a cni.h header file anywhere on my system. Should there be
one? If not, does any version of Strawberry Perl include support for GCJ /
gcc-java? If so, which?
I cannot find enough information on the web to determine:
(1) Whether this is an issue with your distribution, or
(2) Whether it is intentional that users who want to use the Java
capability have to install gcc-java separately on their own (instructions
are where?), or
(3) Whether you don't ship the gcc-java facility specifically because you
know it doesn't work with the software stack (MinGW etc.) you are using.