[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
autoconf 2.13 and failing tests.
From: |
anthony stuckey |
Subject: |
autoconf 2.13 and failing tests. |
Date: |
Thu, 12 Apr 2001 16:05:55 -0500 |
Long story, because I'm not actually sure how to even report this to
get it fixed.
Autoconf 2.1.3 as shipped by Apple in MacOS X seems to include macros
that do not test for malloc() properly, causing test failures.
[localhost:/usr/bin] stuckey% ./autoconf --version
Autoconf version 2.13
[localhost:/usr/bin] stuckey% uname -a
Darwin localhost 1.3 Darwin Kernel Version 1.3: Thu Mar 1 06:56:40 PST
2001; root:xnu/xnu-123.5.obj~1/RELEASE_PPC Power Macintosh powerpc
[localhost:/usr/bin] stuckey%
echo $ac_n "checking for working mmap""... $ac_c" 1>&6
echo "configure:2152: checking for working mmap" >&5
if eval "test \"`echo '$''{'ac_cv_func_mmap_fixed_mapped'+set}'`\" = set";
then
echo $ac_n "(cached) $ac_c" 1>&6
else
if test "$cross_compiling" = yes; then
ac_cv_func_mmap_fixed_mapped=no
else
cat > conftest.$ac_ext <<EOF
#line 2160 "configure"
#include "confdefs.h"
[..]
#ifdef __cplusplus
extern "C" { void *malloc(unsigned); }
#else
char *malloc();
#endif
The problem is that the char* malloc defined here conflicts with the
void* malloc defined in /usr/include/stdlib.h. Thus the code sample does
not compile, and the test is considered failed.
Does this need to go into the Darwin bug tracking database, the
Autoconf bug database, or what?
--
Anthony Stuckey address@hidden
System Administrator, students.uiuc.edu
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- autoconf 2.13 and failing tests.,
anthony stuckey <=