This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
".so" stands for Shared Object, and it's the Linux version of a DLL. A 64-bit .so would be expected to have 64-bit instructions in it, so any attempt to use it on a 32-bit machine would get a quick program fault the first time one of those 64-bit instructions attempted to execute. The necessary hardware doesn't exist on a 32-bit CPU. Going the other direction is OK, since the 64-bit instruction set is a superset of the 32-bit one.
I'd need more information, but it appears you've managed to incorrectly install all or part of a 64-bit software product on your machine. The results are likely to be totally unpredictable. Except I predict that Bad Things will probably happen.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Oct 27, 2009
Thanks for the information. What you said is correct may be. i.e improper installation is the problem in this case.
I was workign on a 32-bit linux server where apache is already installed or it came by defalut i donno.
So, when i try to up the machine with services httpd restart then i'm seeing the prob. that not able to load mod_proxy.
fo which when i tried to see the file with the command [root@server modules]# file /etc/httpd/modules/mod_proxy*
i'm seeing them as
/etc/httpd/modules/mod_proxy.so: ELF 64-bit LSB shared object, version 1, stripped
which must be non-stripped, ELF 32-bit format.
So i downlaoded and apache server and tried to generate the mod_proxy.so with the command
apxs -c -o mod_proxy.so mod_proxy.c proxy_util.c
but this is giving error as
mod_proxy.c:23:24: mod_status.h: No such file or directory
apxs:Break: Command failed with rc=1
Can you let me know, am i going in correct way or not? and is there any other way to deal with this issue.