Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've previously rebuilt the nginx .deb package with the auth_pam module included in Ubuntu 10.04.

Here are the instructions I'm following: [http://web.iti.upv.es/~sto/nginx/ngx_http_auth_pam_module-1.2/][1]

However, when attempting to run dpkg-buildpackage to do the same in Ubuntu 11.04 I'm receiving the following error:

root@eeepc:~/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54# dpkg-buildpackage
dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2
dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): 
dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2
dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2
dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): -Wl,-Bsymbolic-functions
dpkg-buildpackage: source package nginx
dpkg-buildpackage: source version 0.8.54-4+authpam1
dpkg-buildpackage: source changed by root <root@eeepc>
dpkg-buildpackage: host architecture i386
>dpkg-source --before-build nginx-0.8.54
>debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp
rm -f config.sub config.guess
dh_clean
rm -rf /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/debian/build-*
>dpkg-source -b nginx-0.8.54
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building nginx using existing ./nginx_0.8.54.orig.tar.gz
dpkg-source: info: building nginx in nginx_0.8.54-4+authpam1.debian.tar.gz
dpkg-source: info: building nginx in nginx_0.8.54-4+authpam1.dsc
>debian/rules build
dh_testdir
mkdir -p /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/debian/build-full
cp -Pa /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/auto /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/debian/build-full/
cp -Pa /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/conf /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/debian/build-full/
cp -Pa /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/configure /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/debian/build-full/
cp -Pa /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/contrib /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/debian/build-full/
cp -Pa /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/src /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/debian/build-full/
dh_testdir
cp -f /usr/share/misc/config.sub config.sub
dh_testdir
cp -f /usr/share/misc/config.guess config.guess
cd /root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/debian/build-full && ./configure \
>>--conf-path=/etc/nginx/nginx.conf \
>>--error-log-path=/var/log/nginx/error.log \
>>--http-client-body-temp-path=/var/lib/nginx/body \
>>--http-fastcgi-temp-path=/var/lib/nginx/fastcgi \
>>--http-log-path=/var/log/nginx/access.log \
>>--http-proxy-temp-path=/var/lib/nginx/proxy \
>>--http-scgi-temp-path=/var/lib/nginx/scgi \
>>--http-uwsgi-temp-path=/var/lib/nginx/uwsgi \
>>--lock-path=/var/lock/nginx.lock \
>>--pid-path=/var/run/nginx.pid \
>>--with-debug \
>>--with-http_addition_module \
>>--with-http_dav_module \
>>--with-http_geoip_module \
>>--with-http_gzip_static_module \
>>--with-http_image_filter_module \
>>--with-http_realip_module \
>>--with-http_stub_status_module \
>>--with-http_ssl_module \
>>--with-http_sub_module \
>>--with-http_xslt_module \
>>--with-ipv6 \
>>--with-sha1=/usr/include/openssl \
>>--with-md5=/usr/include/openssl \
>>--with-mail \
>>--with-mail_ssl_module \
>>--add-module=/root/src/ngx_http_auth_pam_module-1.2/nginx-0.8.54/debian/modules/nginx-upstream-fair \
>>--add-module=./debian/ngx_http_auth_pam_module \
         >config.status.full
make: *** [config.status.full] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
share|improve this question
    
The relevant error message is in the part you cut. Always include full error transcripts. –  Gilles Dec 4 '11 at 16:07
    
Added the full output. –  Guy Heckman Dec 10 '11 at 15:24
    
add the config.status.full, too. –  sendmoreinfo Feb 13 '12 at 19:33

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.