view auto/endianess @ 4065:227a819b46db

Proper setting of read->eof in pipe code. Setting read->eof to 0 seems to be just a typo. It appeared in nginx-0.0.1-2003-10-28-18:45:41 import (r164), while identical code in ngx_recv.c introduced in the same import do actually set read->eof to 1. Failure to set read->eof to 1 results in EOF not being generally detectable from connection flags. On the other hand, kqueue won't report any read events on such a connection since we use EV_CLEAR. This resulted in read timeouts if such connection was cached and used for another request.
author Maxim Dounin <mdounin@mdounin.ru>
date Thu, 01 Sep 2011 15:10:41 +0000
parents 694d285ec752
children d620f497c50f
line wrap: on
line source


# Copyright (C) Igor Sysoev


echo $ngx_n "checking for system endianess ...$ngx_c"
echo >> $NGX_ERR
echo "checking for system endianess" >> $NGX_ERR


cat << END > $NGX_AUTOTEST.c

int main() {
    int i = 0x11223344;
    char *p;

    p = (char *) &i;
    if (*p == 0x44) return 0;
    return 1;
}

END

ngx_test="$CC $CC_TEST_FLAGS $CC_AUX_FLAGS \
          -o $NGX_AUTOTEST $NGX_AUTOTEST.c $NGX_LD_OPT $ngx_feature_libs"

eval "$ngx_test >> $NGX_AUTOCONF_ERR 2>&1"

if [ -x $NGX_AUTOTEST ]; then
    if $NGX_AUTOTEST >/dev/null 2>&1; then
        echo " little endianess"
        have=NGX_HAVE_LITTLE_ENDIAN . auto/have
    else
        echo " big endianess"
    fi

    rm $NGX_AUTOTEST*

else
    rm $NGX_AUTOTEST*

    echo
    echo "$0: error: can not detect system endianess"
    exit 1
fi