sdfgsd sergserg wrote:
This is done through HP's testdrive program,
the platform is HP-UX 11i v2 rp3410 [EMAIL PROTECTED] 8800 PA-RISC
perl is: 5.8.0
the error is:

spe191> make
        cd "src/modules/perl" && make
        gcc -I/house/doink123/mod_perl-2.0.0-RC1/src/modules/perl 
-I/house/doink123/mod_perl-2.0.0-RC1/xs -I/house/doink123/ap_hpux_rp/include 
-I/house/doink123/ap_hpux_rp/include  -I/house/doink123/ap_hpux_rp/include 
-D_POSIX_C_SOURCE=199506L -D_REENTRANT -D_HPUX_SOURCE -fPIC -mpa-risc-1-1 
-fno-strict-aliasing -I/opt/perl/lib/5.8.0/PA-RISC1.1-thread-multi/CORE 
-DMOD_PERL -DMP_COMPAT_1X -DHPUX11 -D_XOPEN_SOURCE_EXTENDED -O -fPIC \
        -c mod_perl.c && mv mod_perl.o mod_perl.lo
sh: gcc:  not found.
*** Error exit code 127

Stop.
*** Error exit code 1

You posted earlier:

Platform: HP-UX 11i v2 rp3410 [EMAIL PROTECTED] 8800 PA-RISC
Server: Apache 2.0.52 (default install (./configure --prefix=/path/to/dir))
Perl:

Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration:
Platform:
osname=hpux, osvers=11.00, archname=PA-RISC1.1-thread-multi
config_args='-des -Dcc=gcc -Dcf_by=ActiveState
[...]
Compiler:
cc='gcc', ccflags ='-D_POSIX_C_SOURCE=199506L -D_REENTRANT -D_HPUX_SOURCE -f
[...]
ccversion='', gccversion='3.2 20020708 (experimental)', gccosandvers='hpux11
.00'


So your perl was compiled with gcc 3.2, but apparently you don't have it on that system. (as if it was built elsewhere). That's the explanation for the problem you see. You need to have the same compiler you've built perl with.

--
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Reply via email to