On Thu, Aug 07, 2003 at 07:50:42AM +0200, Tassilo von Parseval wrote:
> I have had the same symptoms with my XS modules under these Solaris
> machines (the ones on Sourceforge's compile-farm). For me these problems
> went away when putting suncc into ANSI mode:
>
> perl Makefile.PL CCFLAGS=-Xa
Ok, that fixed those warnings, but caught my bad habit of using C++
style comments in a few places. That's good.
But now I get a few of these:
"Aspell.xs", line 203: warning: argument #1 is incompatible with prototype:
prototype: pointer to char : "/usr/perl5/5.00503/sun4-solaris/CORE/proto.h",
line 355
Where I'm passing a const *char to newSVpv which takes a char *.
bash-2.03$ fgrep newSVpv "/usr/perl5/5.00503/sun4-solaris/CORE/proto.h"
VIRTUAL SV* newSVpv _((char* s, STRLEN len));
Is that the same as on Linux with 5.8?
[EMAIL PROTECTED]:~$ fgrep newSVpv /usr/lib/perl/5.8.0/CORE/proto.h
PERL_CALLCONV SV* Perl_newSVpv(pTHX_ const char* s, STRLEN len);
Is there something I should be doing in my xs code to suppress those or
deal with both cases?
Still, my module isn't loading on that SourceForge machine.
bash-2.03$ ldd blib/arch/auto/Text/Aspell/Aspell.so
libaspell.so.15 => /home/users/w/wh/whmoseley/aspell/lib/libaspell.so.15
libucb.so.1 => (file not found)
[...]
Fine! I'll add -L/usr/ucblib -lucb to my LIBS.
Argh -- so as a module writer how am I suppose to deal with the platform
specific issues? Within an hour of uploading to PAUSE a cpan tester
filed a failed report. I have no idea what didn't work on their system,
could have been the -Xa issue, or the missing libucb library, or they
had the wrong Aspell C library installed.
BTW -- do you find those Solaris SF machines very slow?
--
Bill Moseley
[EMAIL PROTECTED]
