Front page | perl.perl5.porters |
Postings from March 2008
Begin forwarded message:
>
> Automated smoke report for 5.11.0 patch 33456
> Tullamore.local: iMac G5 (1.6 GHz) (macppcG5/1 cpu)
> on darwin - 9.2.0 (Mac OS X)
> using cc version 4.0.1 (Apple Inc. build 5465)
> smoketime 8 hours 40 minutes (average 1 hour 5 minutes)
>
> Summary: PASS
>
> ...
>
> Locally applied patches:
> DEVEL
> SMOKE33456
>
> Compiler messages(gcc):
> hv.c: In function 'S_more_he':
> hv.c:45: warning: implicit declaration of function 'malloc_good_size'
> av.c: In function 'Perl_av_extend':
> av.c:136: warning: implicit declaration of function 'malloc_size'
> sv.c: In function 'S_more_bodies':
> sv.c:1048: warning: implicit declaration of function
> 'malloc_good_size'
> sv.c: In function 'Perl_sv_grow':
> sv.c:1508: warning: implicit declaration of function 'malloc_size'
> perlio.c: In function 'PerlIOStdio_set_ptrcnt':
> perlio.c:3407: warning: pointer targets in assignment differ in
> signedness
> POSIX.c: In function 'XS_POSIX_cuserid':
> POSIX.c:4190: warning: cast to pointer from integer of different size
The bleats about malloc_good_size and malloc_size are a consequence of
the need to include <malloc/malloc.h> to get the prototypes on Mac OS
X. (The header does nothing else relevant to perl: it seems to define
a lot of undocumented instrumentation.) Configure is not currently
checking for it. I suspect it needs yet another config variable, an
addition -- probably just with with inhdr -- around here:
: see if this is a malloc.h system
: we want a real compile instead of Inhdr because some systems have a
: malloc.h that just gives a compile error saying to use stdlib.h
instead
echo " "
$cat >try.c <<EOCP
#include <stdlib.h>
#include <malloc.h>
int main () { return 0; }
EOCP
set try
if eval $compile; then
echo "<malloc.h> found." >&4
val="$define"
else
echo "<malloc.h> NOT found." >&4
val="$undef"
fi
$rm_try
set i_malloc
eval $setvar
in Configure, and the corresponding tweaks to config_h.SH and Porting/
Glossary. If somebody will confirm this, I'll come up with a patch. (I
won't touch metaconfig, though.)
--
Dominic Dunlop
Thread Previous