Loading nginx on 64bit os

Server NGINX
1

hi,

i have a problem here. in php, apache i am able to define the libdir for
my 64bit centos.

nginx doesn’t have this configuration option. it just hit me. i am
trying nginx 0.6.25.

if anyone got it to work on 64bit linux based os, please give me the
hint i need to get the show rolling.

2

On Fri, Jan 18, 2008 at 06:12:06PM +0100, Stefanita rares Dumitrescu
wrote:

hi,

i have a problem here. in php, apache i am able to define the libdir for
my 64bit centos.

nginx doesn’t have this configuration option. it just hit me. i am
trying nginx 0.6.25.

if anyone got it to work on 64bit linux based os, please give me the
hint i need to get the show rolling.

I’m not using centos, but I’m building and using nginx on sparc64 &
amd64 OpenBSD using nothing special versus building on 32-bit x86.

What errors are you getting?

3

On Fri, 2008-01-18 at 18:12 +0100, Stefanita rares Dumitrescu wrote:

hi,

i have a problem here. in php, apache i am able to define the libdir for
my 64bit centos.

nginx doesn’t have this configuration option. it just hit me. i am
trying nginx 0.6.25.

Why do you need to specify libdir? Are you running a hybrid 32/64-bit
system?

if anyone got it to work on 64bit linux based os, please give me the
hint i need to get the show rolling.

I’m running 64-bit (Opteron) on Gentoo, but didn’t do anything special
to make it work.

Cliff

4

hi,
I am using nginx on 64 and 32 bit Centos 4.6.

This works for me:

NGINX_PATH=/opt/nginx
if [ “$SERVER_HWTYPE”=“x86_64” ]; then
MD5_PATH="/usr/lib64"
else
MD5_PATH="/usr/lib"
fi
yum -y install pcre pcre-devel openssl-devel
./configure
–prefix=$NGINX_PATH
–with-http_stub_status_module
–without-http_charset_module
–without-http_gzip_module
–without-http_ssi_module
–without-http_userid_module
–without-http_geo_module
–without-http_map_module
–without-http_referer_module
–without-http_memcached_module
–without-http_browser_module
–without-mail_pop3_module
–without-mail_imap_module
–without-mail_smtp_module
–with-http_ssl_module
–with-md5=$MD5_PATH
make
make install

Sincerely,
Martin Minka

5

El Fri, 18 Jan 2008 09:36:41 -0800
Cliff W. [email protected] escribió:

Why do you need to specify libdir? Are you running a hybrid 32/64-bit
system?

if anyone got it to work on 64bit linux based os, please give me the
hint i need to get the show rolling.

I’m running 64-bit (Opteron) on Gentoo, but didn’t do anything special
to make it work.

Gentoo on x86-64 systems follows the FHS strictly, so /lib is a
symlink to /lib64 and /usr/lib to /usr/lib64… that’s why you don’t
need anything special to link against 64-bit libraries. Other distros
do the opposite (i.e. linking /lib to /lib32 and so on) because that
is «supposed to be more compatible».

I haven’t used pure 64-bit systems, but it is supposed that /lib
and /usr/lib are not symlinks but true directories in that case. (At
least that’s what I read in the FHS…)

Regards,

6

Adrian P. wrote:

El Fri, 18 Jan 2008 09:36:41 -0800
Cliff W. [email protected] escribió:

Why do you need to specify libdir? Are you running a hybrid 32/64-bit
system?

if anyone got it to work on 64bit linux based os, please give me the
hint i need to get the show rolling.

I’m running 64-bit (Opteron) on Gentoo, but didn’t do anything special
to make it work.

Gentoo on x86-64 systems follows the FHS strictly, so /lib is a
symlink to /lib64 and /usr/lib to /usr/lib64… that’s why you don’t
need anything special to link against 64-bit libraries. Other distros
do the opposite (i.e. linking /lib to /lib32 and so on) because that
is «supposed to be more compatible».

I haven’t used pure 64-bit systems, but it is supposed that /lib
and /usr/lib are not symlinks but true directories in that case. (At
least that’s what I read in the FHS…)

Regards,

cd /usr
&& make clean
&& CFLAGS="-O2 -fomit-frame-pointer -pipe " CC=“gcc”
./configure
&& make libz.a
make[2]: Entering directory /usr' make[2]: *** No rule to make target clean’. Stop.
make[2]: Leaving directory /usr' make[1]: *** [/usr/libz.a] Error 2 make[1]: Leaving directory /root/kit/nginx-0.6.25’
make: *** [build] Error 2

./configure works fine. i do :

./configure --prefix=/usr/local/nginx
–conf-path=/etc/nginx.conf
–error-log-path=/var/log/nginx
–lock-path=/tmp/nginx.lock
–user=nobody
–group=nobody
–with-http_ssl_module
–with-http_addition_module
–with-http_sub_module
–with-http_flv_module
–with-http_gzip_static_module
–with-http_stub_status_module
–with-mail
–with-zlib=/usr
–with-debug

once i do make … the error is below.

7

Hello!

On Sun, Jan 20, 2008 at 08:54:43PM +0100, Stefanita rares Dumitrescu
wrote:

I’m running 64-bit (Opteron) on Gentoo, but didn’t do anything special
least that’s what I read in the FHS…)
make[2]: Leaving directory `/usr’
–lock-path=/tmp/nginx.lock
–user=nobody
–group=nobody
–with-http_ssl_module
–with-http_addition_module
–with-http_sub_module
–with-http_flv_module
–with-http_gzip_static_module
–with-http_stub_status_module
–with-mail
–with-zlib=/usr \

There is no zlib sources in /usr, I suppose. So remove
‘–with-zlib=/usr’
from configure and try again.

Maxim D.

8

Stefanita rares Dumitrescu wrote:

Adrian P. wrote:

El Fri, 18 Jan 2008 09:36:41 -0800
Cliff W. [email protected] escribió:

Why do you need to specify libdir? Are you running a hybrid 32/64-bit
system?

if anyone got it to work on 64bit linux based os, please give me the
hint i need to get the show rolling.

I’m running 64-bit (Opteron) on Gentoo, but didn’t do anything special
to make it work.

Gentoo on x86-64 systems follows the FHS strictly, so /lib is a
symlink to /lib64 and /usr/lib to /usr/lib64… that’s why you don’t
need anything special to link against 64-bit libraries. Other distros
do the opposite (i.e. linking /lib to /lib32 and so on) because that
is «supposed to be more compatible».

I haven’t used pure 64-bit systems, but it is supposed that /lib
and /usr/lib are not symlinks but true directories in that case. (At
least that’s what I read in the FHS…)

Regards,

cd /usr
&& make clean
&& CFLAGS="-O2 -fomit-frame-pointer -pipe " CC=“gcc”
./configure
&& make libz.a
make[2]: Entering directory /usr' make[2]: *** No rule to make target clean’. Stop.
make[2]: Leaving directory /usr' make[1]: *** [/usr/libz.a] Error 2 make[1]: Leaving directory /root/kit/nginx-0.6.25’
make: *** [build] Error 2

./configure works fine. i do :

./configure --prefix=/usr/local/nginx
–conf-path=/etc/nginx.conf
–error-log-path=/var/log/nginx
–lock-path=/tmp/nginx.lock
–user=nobody
–group=nobody
–with-http_ssl_module
–with-http_addition_module
–with-http_sub_module
–with-http_flv_module
–with-http_gzip_static_module
–with-http_stub_status_module
–with-mail
–with-zlib=/usr
–with-debug

once i do make … the error is below.

pure 64bit .

            src/mail/ngx_mail_proxy_module.c

gcc -c -O -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter
-Wno-unused-function -Wunused-variable -Wunused-value -Werror -g -I
src/core -I src/event -I src/event/modules -I src/os/unix -I /usr -I
objs
-o objs/ngx_modules.o
objs/ngx_modules.c
cd /usr
&& make clean
&& CFLAGS="-O2 -fomit-frame-pointer -pipe " CC=“gcc”
./configure
&& make libz.a
make[2]: Entering directory /usr' make[2]: *** No rule to make target clean’. Stop.
make[2]: Leaving directory /usr' make[1]: *** [/usr/libz.a] Error 2 make[1]: Leaving directory /root/kit/nginx-0.6.25’
make: *** [build] Error 2

9

Stefanita rares Dumitrescu wrote:

Stefanita rares Dumitrescu wrote:

Adrian P. wrote:

El Fri, 18 Jan 2008 09:36:41 -0800
Cliff W. [email protected] escribió:

Why do you need to specify libdir? Are you running a hybrid 32/64-bit
system?

if anyone got it to work on 64bit linux based os, please give me the
hint i need to get the show rolling.

I’m running 64-bit (Opteron) on Gentoo, but didn’t do anything special
to make it work.

Gentoo on x86-64 systems follows the FHS strictly, so /lib is a
symlink to /lib64 and /usr/lib to /usr/lib64… that’s why you don’t
need anything special to link against 64-bit libraries. Other distros
do the opposite (i.e. linking /lib to /lib32 and so on) because that
is «supposed to be more compatible».

I haven’t used pure 64-bit systems, but it is supposed that /lib
and /usr/lib are not symlinks but true directories in that case. (At
least that’s what I read in the FHS…)

Regards,

cd /usr
&& make clean
&& CFLAGS="-O2 -fomit-frame-pointer -pipe " CC=“gcc”
./configure
&& make libz.a
make[2]: Entering directory /usr' make[2]: *** No rule to make target clean’. Stop.
make[2]: Leaving directory /usr' make[1]: *** [/usr/libz.a] Error 2 make[1]: Leaving directory /root/kit/nginx-0.6.25’
make: *** [build] Error 2

./configure works fine. i do :

./configure --prefix=/usr/local/nginx
–conf-path=/etc/nginx.conf
–error-log-path=/var/log/nginx
–lock-path=/tmp/nginx.lock
–user=nobody
–group=nobody
–with-http_ssl_module
–with-http_addition_module
–with-http_sub_module
–with-http_flv_module
–with-http_gzip_static_module
–with-http_stub_status_module
–with-mail
–with-zlib=/usr
–with-debug

once i do make … the error is below.

pure 64bit .

            src/mail/ngx_mail_proxy_module.c

gcc -c -O -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter
-Wno-unused-function -Wunused-variable -Wunused-value -Werror -g -I
src/core -I src/event -I src/event/modules -I src/os/unix -I /usr -I
objs
-o objs/ngx_modules.o
objs/ngx_modules.c
cd /usr
&& make clean
&& CFLAGS="-O2 -fomit-frame-pointer -pipe " CC=“gcc”
./configure
&& make libz.a
make[2]: Entering directory /usr' make[2]: *** No rule to make target clean’. Stop.
make[2]: Leaving directory /usr' make[1]: *** [/usr/libz.a] Error 2 make[1]: Leaving directory /root/kit/nginx-0.6.25’
make: *** [build] Error 2

i am stucked… really.

cd /usr/lib
&& make clean
&& CFLAGS="-O2 -fomit-frame-pointer -pipe " CC=“gcc”
./configure
&& make libz.a
make[2]: Entering directory /usr/lib64' make[2]: *** No rule to make target clean’. Stop.
make[2]: Leaving directory /usr/lib64' make[1]: *** [/usr/lib/libz.a] Error 2 make[1]: Leaving directory /root/kit/nginx-0.6.25’
make: *** [build] Error 2

make stops

[root@mars nginx-0.6.25]# ls -la /usr/lib/libz.a
-rwxr-xr-x 1 root root 108660 Jan 9 2007 /usr/lib/libz.a

libz.a exists , and it’s the 64 bit one.

[root@mars nginx-0.6.25]# rpm -qf /usr/lib/libz.a
zlib-devel-1.2.3-3

[root@mars nginx-0.6.25]# yum list |grep zlib
zlib.x86_64 1.2.3-3
installed
zlib-devel.x86_64 1.2.3-3
installed