timer23
/
efl
forked from enlightenment/efl
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

checking for NULL=0 is too much. 

particularly if all you do is warning, the whole EFL would stop
working due our "if (ptr)" checks.



SVN revision: 77793
This commit is contained in:
Gustavo Sverzut Barbieri 2012-10-10 20:00:43 +00:00
parent 4d35e4ca03
commit 06e48b4296
1 changed files with 0 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
configure.ac
View File

@ -726,30 +726,6 @@ AC_CHECK_HEADERS(netinet/in.h unistd.h)
### Checks for compiler characteristics
# Check whether the null pointer is zero on this arch
AC_TRY_RUN(
[
#include <stdlib.h>
#include <inttypes.h>
int main (int argc, char **argv) {
void *foo = NULL;
uintptr_t bar = (uintptr_t)foo;
return (uintptr_t)foo;
}
],
[have_null="yes"],
[have_null="no"],
[
AC_MSG_WARN([Cannot check when cross-compiling -- assuming null is okay])
have_null="yes"
])
AC_MSG_CHECKING([value of the null pointer])
AC_MSG_RESULT([${have_null}])
if test ! "x${have_null}" = "xyes" ; then
AC_MSG_WARN([Your system is a bit too funny, eet might not work properly])
fi
EFL_CHECK_COMPILER_FLAGS([EET], [-Wshadow -Wpointer-arith])
### Checks for linker characteristics