RetroSearch Browse

Sat Jan 17 02:47:54 EST 2004 · https://mail.python.org/pipermail/python-dev/2004-January/042045.html

Skip Montanaro wrote:
> In configure.in there is a check for bad exec* prototypes:
> 
>     if test "$have_prototypes" = yes; then
>     bad_prototypes=no
>     AC_MSG_CHECKING(for bad exec* prototypes)
>     AC_TRY_COMPILE([#include <unistd.h>], [char **t;execve("@",t,t);], ,
>         AC_DEFINE(BAD_EXEC_PROTOTYPES, 1,
>         [Define if your <unistd.h> contains bad prototypes for exec*()
>         (as it does on SGI IRIX 4.x)]) 
>         bad_prototypes=yes
>     )
>     AC_MSG_RESULT($bad_prototypes)
>     fi
> 
> Since we assume a proper ANSI C compiler at this point, can we get rid of
> this test?

That code is ancient.  The fi on the last line is still from revision 
1.1 in 1993!
I wrote the original version of this and Guido incorporated it into the 
Python configure.  I think it can go, especially since IRIX 4 support 
has been deleted.

-- 
Sjoerd Mullender <sjoerd at acm.org>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-January/042045.html below:

[Python-Dev] bad exec* prototypes check