64Bit binaries of httpd and mod_*.so for PARISC2 on B.11.11 required

[Ralph Grothe]

Hello,

I am a bit rushed to get installed an Apache >= 2.0.48 quickly as this is needed for some SAP Content Server that some SAP blokes want to install on this B.11.11 host.
I downloaded from software.hp.com their parisc B.11.11 port of hpuxwsApache and installed that.
The depot seems to insinuate that the depot contains 64bit binaries as well by designating these fileset names by an apppended 2.

see

# uname -srv;model;getconf KERNEL_BITS
HP-UX B.11.11 U
9000/800/L2000-44
64

# swlist -l fileset hpuxwsApache.hpuxwsAPACHE.APACHE2|tail -3

# hpuxwsApache B.2.0.58.01 HP-UX Apache-based Web Server (with IPv6 support
)
hpuxwsApache.hpuxwsAPACHE.APACHE2 B.2.0.58.01 2.0.58 base (PA Binaries)


However, the only binary in the fileset seems to be a 32bit build.

# swlist -l file hpuxwsApache.hpuxwsAPACHE.APACHE2|awk '$NF~/httpd$/'
/opt/hpws/apache/bin/httpd


# file /opt/hpws/apache/bin/httpd
/opt/hpws/apache/bin/httpd: PA-RISC1.1 shared executable dynamically linked -not stripped

# /opt/hpws/apache/bin/httpd -V
Server version: Apache/2.0.58 HP-UX_Apache-based_Web_Server
Server built: Dec 18 2006 15:31:15
Server's Module Magic Number: 20020903:12
Server loaded: APR 0.9.12, APR-UTIL 0.9.12
Compiled using: APR 0.9.12, APR-UTIL 0.9.12
Architecture: 32-bit
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/worker"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PROC_PTHREAD_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D APR_PROCESS_LOCK_IS_GLOBAL
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D HTTPD_ROOT="/opt/hpws/apache"
-D DEFAULT_CHROOT_DIR=""
-D SUEXEC_BIN="/opt/hpws/apache/bin/suexec"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"


The same seems to apply for the Apache modules

# file /opt/hpws/apache/modules/mod_*|grep -cv PA-RISC1.1
0


When the SAP people try to install their stuff they get error screens that indicate a 32 vs. 64 bit clash.
See, these are the modules their Content Server stuff provides:

# file ~t01cs/modules/*
/usr/sap/T01/cs/modules/libsapsecu.1.so: ELF-64 shared object file - PA-RISC 2.0 (LP64)
/usr/sap/T01/cs/modules/libsapsecu.so: ELF-64 shared object file - PA-RISC 2.0 (LP64)
/usr/sap/T01/cs/modules/mod_sapcs.so: ELF-64 shared object file - PA-RISC 2.0 (LP64)
/usr/sap/T01/cs/modules/mod_sapcs2.1.so: ELF-64 shared object file - PA-RISC 2.0 (LP64)
/usr/sap/T01/cs/modules/mod_sapcs2.so: ELF-64 shared object file - PA-RISC 2.0 (LP64)
/usr/sap/T01/cs/modules/mod_sapcsc.so: ELF-64 shared object file - PA-RISC 2.0 (LP64)
/usr/sap/T01/cs/modules/mod_sapcsc2.so: ELF-64 shared object file - PA-RISC 2.0 (LP64)


Where can I get an Apache port that matches those?

Regards
Ralph

[Steven E. Protter]

Shalom Ralph,

Unlikely apache is going to do something for you just because you ask or need it really bad.

After all they aren't making any money off this deal. They provide code that works as they see fit.

Options:

1) Compile apache yourself. Its open source. There is no reason why you can't try to compile it. Lots of Luck, it may not be easy.

2) Contact HP and ask them to release a full 64 bit version. They won't do it fast, but they MAY do it.

I think based on the error messages you are using the wrong verion of SAP. I'm not sure an ELF-64 bit binary is every going to workon PA RISC 2.0, though I may be misinterpreting the error output.

SEP

[Ralph Grothe]

Hi Steven,

meanwhile I did what you suggested, and asked HP support.
I acknowledge that they may not be too interesetd in digging out an ad-hoc solution, as it is merely complementary OpenSource software they added because of its sheer widespread use.
However, they are quite helpful as I already got a phone call.
The depot's description clearly indicates that it is worth for installation on either 32 or 64bit platform, and the selection of the appropiate filesets should be made autoguessingly by the swinstaller, and my installed filesets seem to indicate that as well.
Looks as if some quirk in some concealed system file made the swinstaller guess that we are on a 32bit platform?

It even may well be as you assumed that SAP came up with completely wrong binaries.
It took my poor fellow SAP admins quite some pain and exchange with SAP support to get all sorts of different downloads and CDs/DVDs offered.

I know that Apache sources are available.
I have compiled different versions of it with different features on different OSes before.
Although I most likely only need a vanilla build for this SAP crap I hoped to avoid the hassle of manual automake configuration sprees.

[rick jones · Accepted solution]

I'm not familiar with the Apache depots, but will point-out that something which says it can be installed on both 32-bit and 64-bit platforms does not in and of itself imply that there is a 64-bit binary in the package, since a 64-bit HP-UX kernel can run 32-bit binaries just fine and dandy...

It may be necessary to recompile the sources yourself adding a +DD64, or perhaps the Porting Archive folks have a 64-bit compilation already:

http://hpux.connect.org.uk/ or its mirrors

[Dennis Handly]

On Integrity there are both 32 and 64 bit versions available.

>SEP: I'm not sure an ELF-64 bit binary is every going to work on PA RISC 2.0

These are 64 bit for PA-RISC 2.0.

[Ralph Grothe]

Hi all,

thanks for your thoughts.
I just would like to give you some feedback.
This morning I received a call in response to my HP support case.
They were sad to have to confirm that the official Apache depots for PARISC published by HP indeed weren't 64bit builds, but as Rick correctly stated, executable as 32bit binaries on a 64bit capable platform.
The supporter also mentioned that it probably would be too much ado to get a 64bit build from HP.
But I really don't mind and had the case closed because compiling a 64bit binary really was painless.
Although I exported a CFLAGS=+DD64 as Rick suggested I think this really wouldn't have been necessary since during the make that +DD64 overrode other flags that were deemed appropiate by the autoconf configure run
e.g.

"cc: warning 441: Previous '+DA' or '+DD' option overridden by '+DD64' option."

Apart from theses repeating but negligeable warnings the make went absolutely smoothly.

Now we are in possesion of 64bit Apache binaries and modules, and the follow-on SAP CS installation (which is currently in progress) so far looks promising.

# /opt/apache/bin/httpd -V
Server version: Apache/2.0.59
Server built: Mar 1 2007 10:27:23
Server's Module Magic Number: 20020903:12
Server loaded: APR 0.9.12, APR-UTIL 0.9.12
Compiled using: APR 0.9.12, APR-UTIL 0.9.12
Architecture: 64-bit
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D HTTPD_ROOT="/opt/apache"
-D SUEXEC_BIN="/opt/apache/bin/suexec"
-D DEFAULT_PIDLOG="logs/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_LOCKFILE="logs/accept.lock"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"

# file /opt/apache/modules/mod_*|grep -c LP64
29