Simon Bertrang wrote:
Hi,
i'm trying to update mp2 but it fails to finish compilation.
Specifically, it fails at Base64:
...
cp Base64.pm ../../../blib/lib/APR/Base64.pm
/usr/bin/perl /usr/libdata/perl5/ExtUtils/xsubpp  -typemap 
/usr/libdata/perl5/ExtUtils/typemap -typemap 
/usr/ports/www/ap2-mod_perl/w-ap2-mod_perl-2.0.4/mod_perl-2.0.4/xs/typemap  Base64.xs > 
Base64.xsc && mv Base64.xsc Base64.c
cc -c  -I/usr/ports/www/ap2-mod_perl/w-ap2-mod_perl-2.0.4/mod_perl-2.0.4/src/modules/perl 
-I/usr/ports/www/ap2-mod_perl/w-ap2-mod_perl-2.0.4/mod_perl-2.0.4/xs -I/usr/local/include/apr-1/ 
-I/usr/local/include/apr-1/ -I/usr/local/include/db4 -I/usr/local/include -I/usr/local/include/apache2  
-fno-strict-aliasing -fno-delete-null-pointer-checks -pipe -I/usr/local/include -DMOD_PERL -DMP_COMPAT_1X 
-D_POSIX_THREADS -O2     -DVERSION=\"0.009000\"  -DXS_VERSION=\"0.009000\" -DPIC -fPIC 
"-I/usr/libdata/perl5/amd64-openbsd/5.8.8/CORE"  -DMP_HAVE_APR_LIBS Base64.c
In file included from Base64.xs:24:
/usr/ports/www/ap2-mod_perl/w-ap2-mod_perl-2.0.4/mod_perl-2.0.4/xs/modperl_xs_typedefs.h:67:
 error: syntax error before '*' token
/usr/ports/www/ap2-mod_perl/w-ap2-mod_perl-2.0.4/mod_perl-2.0.4/xs/modperl_xs_typedefs.h:67:
 warning: data definition has no type or storage class
*** Error code 1

Stop in 
/usr/ports/www/ap2-mod_perl/w-ap2-mod_perl-2.0.4/mod_perl-2.0.4/WrapXS/APR/Base64
 (line 92 of /usr/share/mk/sys.mk).
...

I did a lot of testing with mod_perl-2.0.3 yesterday, so i can at least
assure that a working environment hasn't changed in the meantime.
Unfortunately i haven't found a fix for this yet, hence this mail.

Has someone of you an idea where i need to look to get it solved?

Pgollucci found a similar issue with FreeBSD, Gozer posted a patch that may fix it. Suggest trying out the patch:

http://www.gossamer-threads.com/lists/modperl/dev/97018?search_string=Base64.xsc;#97018

HTH,

Fred


Kind regards,
Simon


--
Red Hot Penguin Consulting LLC
mod_perl consulting and implementation
http://www.redhotpenguin.com/

Reply via email to