RHEL 32 vs. 64 Bit, MySQL 5
I have a general question, and then a narrower one. The general question:
On a system with a 64-bit Xeon (Intel EM64T) CPU, how much does one lose (if anything) by installing the 32-bit version of an application instead of the 64-bit version? What happens when the 32-bit app talks to the 64-bit OS? Is there some kind of thunking or context switching that has to happen? If so, is it significantly time consuming?
The narrower question:
I'm installing MySQL 5 on a Dell PowerEdge with a 64-bit Xeon (Intel EM64T) CPU. After installing the 64-bit RPM's, and try to start the Apache web server, I get the following:
[root@edge rhel4-em64t]# service httpd start
Starting httpd: Syntax error on line 6 of /etc/httpd/conf.d/auth_mysql.conf:
Cannot load /etc/httpd/modules/mod_auth_mysql.so into server: libmysqlclient.so.14: cannot open shared object file: No such file or directory
I found out that in this case one must install the "compat" version of the shared library instead of the "standard version".
I've found the 32 bit one (MySQL-shared-compat-5.0.18-0.i386.rpm) but cannot find a 64 bit version. Does it exist? If not, how can I get MySQL 5 to work in 64 bit mode? I'd prefer an rpm to building it myself so that the package manager has knowledge of it.
Should I just use the 32-bit rpm's?
Thanks for any information.
yes you can use 32bit rpms on 64bit
|All times are GMT -5. The time now is 07:26 PM.|