Ritu Kamboj wrote:
> Should we have two directories namely /usr/mysql/32bit and
> /usr/mysql/64bit and have 32bit libraries and server under
> /usr/mysql/32bit and only 64bit server under /usr/mysql/64bit ....or
> it should be more a directory deeper (ie
> /usr/mysql/bin/{32bit/64bit})Follow the Solaris convention. In the bin & lib dir have 32bit objects and a subdir named `isainfo -n` contains 64bit equivalents. A softlink "64" can point to the subdir, so one can set paths without worrying about the hardware. % ls -la /usr/bin/ld -rwxr-xr-x 1 root bin 13780 Aug 26 11:40 /usr/bin/ld % ls -la /usr/bin/`isainfo -n`/ld -rwxr-xr-x 1 root bin 20168 Aug 26 11:40 /usr/bin/amd64/ld % ls -la /lib/libc.so.1 -rwxr-xr-x 1 root bin 1331180 Aug 26 09:40 /lib/libc.so.1 % ls -la /lib/`isainfo -n`/libc.so.1 -rwxr-xr-x 1 root bin 2655800 Aug 26 09:45 /lib/amd64/libc.so.1 % ls -la /lib/64 lrwxrwxrwx 1 root root 5 Sep 21 14:05 /lib/64 -> amd64 Notice there are many fewer binaries in /usr/bin/amd64/ vs. /usr/bin/, so another thing to consider is whether you need 64bit equivalents of everything. At a minimum you'll need 64bit daemons and all libs those might need. If there are simple ancillary executables that don't need 64bit address space maybe those can be only 32bit. As a potential example, maybe the client interface 'mysql' doesn't need 64bit? (Or maybe it does, but something to consider). That should cover it. If you find anything odd w.r.t 64bit MySQL (for instance like in Apache where it had different 32- and 64-bit include files) then bring it up here and we can discuss possible approaches. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
