Re: HP11.00, php 4.3 and mysql
| From: | (Michael Mauch) | Date: | Wed, 26 Mar 2003 03:33:15 +0000 |
| Subject: | Re: HP11.00, php 4.3 and mysql | ||
| References: | 1 | Groups: | php.install |
| Request: | Send a blank email to php-install+get-10424@lists.php.net to get a copy of this message | ||
Madhu <madhu.kangara@t-mobile.com> wrote:
> I am facing heavy challenges trying to compile php as a DSO module into
> apache.
> I have a HP 11.00 OS (B2600) system with gcc 3.1 installed. I don't have
> installed any new patch bundles on this system.
> I am having apache 1.3.26 for HP 11.00 downloaded from HP
> Mysql 4.0.12 binary downloaded from mysql (I was not sucessful in compiling
> mysql source on this m/c)
They only seem to have binaries for HP-UX 11.11. I don't know anything
about HP-UX, but you do probably - is this version mismatch no problem?
> The configure options I gave are as follows
> $
> ./configure --with-mysql=/usr/local/mysql --with-zlib-dir=/usr/local/lib --
> with-apxs=/usr/local/apache/bin/apxs
> conftest -g -O2 -DHPUX11 -D_HPUX_SOURCE -DUSE_HSREGEX -DUSE_EXPAT
> -L/usr/local/lib -L/usr/local/mysql/lib
> -L/usr/local/lib -L/usr/local/lib -L/usr/local -L/usr/local
> conftest.c -lmysqlclient -lz -lz -lcrypt -lm -lnsl -lcrypt 1>&5
> /usr/ccs/bin/ld: /usr/local/mysql/lib/libmysqlclient.a: Not a valid library
> (invalid magic number). Possibly a 64-bit PA archive library (Mismatched
> ABI).
So did you install the 64-bit version or the 32-bit version of MySQL?
And which sort does your gcc build by default?
<http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&threadm=3c5acb6b.866421%40news.tamu.edu&rnum=13&prev=/groups%3Fq%3DPHP%2Bmysql%2BHP/UX%2B64-bit%26hl%3Dde%26lr%3D%26ie%3DUTF-8%26scoring%3Dd%26start%3D10%26sa%3DN>
might be interesting if you don't know much about HP/UX (perhaps you
were just told to install PHP on that machine that you never saw before).
Also you might find the user notes on
<http://www.php.net/manual/en/install.hpux.php>
interesting, although I
didn't find anything related to your current problem.
Regards (from a colleague @t-mobile.de)...
Michael