Package: libnet-arp-perl
Version: 0.8-1
Severity: important

Hi,

Your package is failing to build with the following error:
/usr/bin/make test
make[1]: Entering directory `/build/buildd/libnet-arp-perl-0.8'
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 
'blib/lib', 'blib/arch')" t/*.t
t/ARP....ok
All tests successful.
Files=1, Tests=1,  0 wallclock secs ( 0.06 cusr +  0.01 csys =  0.07 CPU)
PERL_DL_NONLAZY=1 /usr/bin/perl "-Iblib/lib" "-Iblib/arch" test.pl
make[1]: *** [test_dynamic] Segmentation fault
make[1]: Leaving directory `/build/buildd/libnet-arp-perl-0.8'


It looks like you're having this problem on 64 bit arches.

Also, notice the following warnings in the buildd log:
ARP.xs:120: warning: implicit declaration of function 'ether_aton'
ARP.xs:120: warning: cast to pointer from integer of different size
ARP.xs:121: warning: cast to pointer from integer of different size
ARP.xs:130: warning: cast to pointer from integer of different size
[...]
ARP.xs:134: warning: cast to pointer from integer of different size
[...]
ARP.xs:143: warning: implicit declaration of function 'send_packet_bsd'
ARP.xs:149: warning: implicit declaration of function 'send_packet_linux'
[...]
ARP.xs:161: warning: implicit declaration of function 'get_mac_bsd'
ARP.xs:165: warning: implicit declaration of function 'get_mac_linux'
[...]
send_packet_linux.c:30: warning: implicit declaration of function 'strlen'
send_packet_linux.c:30: warning: incompatible implicit declaration of built-in
function 'strlen'
[...]
send_packet_linux.c:35: warning: implicit declaration of function 'htons'
send_packet_linux.c:37: warning: implicit declaration of function 'perror'
send_packet_linux.c:38: warning: implicit declaration of function 'exit'
[...]

Some of those warnings are caused by missing #includes.

The warnings about the cast from pointer to integer and
the other way around probably indicate that there is a 64
bit portability problem.

The others warnings can have as effect that C defaults
to a function returning an int where it should be one
that returns a pointer.  Fixing those warnings might also
fix the segfault.

You really should have a prototype for all functions you
use.


Kurt



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to