My knee-jerk to this was that it was a problem compiling against the new libnewt0.50. Looking into it further I find that I can build using the same gcc on x86 with no problem. xsubpp generates the same code which is handled fine on x86, but chokes on powerpc. I'm running gcc 2.95.1-2 on both systems.
Here is a dump in case any one has an ideas or suggestions: make[2]: Leaving directory `/home/mporter/src/libnewt-perl-1.08/newtlib' /usr/bin/perl -I/usr/lib/perl5/5.005/powerpc-linux -I/usr/lib/perl5/5.005 /usr/lib/perl5/5.005/ExtUtils/xsubpp -typemap /usr/lib/perl5/5.005/ExtUtils/typemap -typemap typemap Newt.xs >xstmp.c && mv xstmp.c Newt.c Please specify prototyping behavior for Newt.xs (see perlxs manual) cc -c -Dbool=char -DHAS_BOOL -D_REENTRANT -DDEBIAN -I/usr/local/include -O2 -DVERSION=\"1.08\" -DXS_VERSION=\"1.08\" -fPIC -I/usr/lib/perl5/5.005/powerpc-linux/CORE Newt.c Newt.c: In function `XS_Newt_va_end': Newt.c:701: cast specifies array type Newt.c: In function `XS_Newt_newtButtonBarv': Newt.c:2684: cast specifies array type Newt.c: In function `XS_Newt_newtWinMessagev': Newt.c:2748: cast specifies array type make[1]: *** [Newt.o] Error 1 make[1]: Leaving directory `/home/mporter/src/libnewt-perl-1.08' make: *** [build-stamp] Error 2 -- Matt Porter [EMAIL PROTECTED] This is Linux Country. On a quiet night, you can hear Windows reboot.
