errors when compiling with 1.16.1

Issue #48 new
RiyadhOmar created an issue

Hello,

I’m getting an error trying to compile Nginx with this module on nginx-1.16.1. Would this still be compatible?

../modules/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.c: In function 'ngx_http_sticky_misc_sha1':
../modules/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.c:176:15: error: 'SHA_DIGEST_LENGTH' undeclared (first use in this function)
u_char hash[SHA_DIGEST_LENGTH];
^
../modules/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.c:176:15: note: each undeclared identifier is reported only once for each function it appears in
../modules/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.c:176:10: error: unused variable 'hash' [-Werror=unused-variable]
u_char hash[SHA_DIGEST_LENGTH];
^
../modules/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.c: In function 'ngx_http_sticky_misc_hmac_sha1':
../modules/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.c:242:15: error: 'SHA_DIGEST_LENGTH' undeclared (first use in this function)
u_char hash[SHA_DIGEST_LENGTH];
^
../modules/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.c:243:12: error: 'SHA_CBLOCK' undeclared (first use in this function)
u_char k[SHA_CBLOCK];
^
../modules/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.c:243:10: error: unused variable 'k' [-Werror=unused-variable]
u_char k[SHA_CBLOCK];
^
../modules/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.c:242:10: error: unused variable 'hash' [-Werror=unused-variable]
u_char hash[SHA_DIGEST_LENGTH];
^
cc1: all warnings being treated as errors
make[1]: *** [objs/addon/nginx-goodies-nginx-sticky-module-ng-08a395c66e42/ngx_http_sticky_misc.o] Error 1
make[1]: Leaving directory `/opt/nginx-source/nginx-1.16.1'
make: *** [build] Error 2

Comments (2)

  1. Gehad Abu Seada

    Hi Riyadah,

    I’m having the same problem. while configuring it with nginx 1.18, how did you recover that?

  2. Log in to comment