I'm hitting dumb stuff that arises from my unfamiliarity with working in a 32/64-bit split universe on a Solaris box.
Is there some magic phrase I can tell configure that will make it realise I want to pick up the 32-bit /opt/mysql50/include/mysql include files, and not the include files that lives at /usr/sfw/include/mysql that it seems to prefer? I can go around editing Makefiles, or even install my own 32-bit mysql client, but there has to be a better way.
Or maybe the information here is out of date:
http://meta.wikimedia.org/wiki/Toolserver/For_users#software
It suggests that I should link to the /opt/mysql50 code for a 32-bit build.
if there's some amazing advantage to compiling all my code for 64 bits, please feel free to convince me. In private email. I think it more likely that I'm just being dumb.
On 12/13/05, Tony Sidaway f.crdfa@gmail.com wrote:
if there's some amazing advantage to compiling all my code for 64 bits, please feel free to convince me. In private email. I think it more likely that I'm just being dumb.
I thought the default on slowarse was to compile for 32bit on x86-64.
Odd.. anyways, most of the time the performance advantage isn't large (much is lost due to the cost of dealing with larger pointers) but for some usage patterns the extra registers (and vastly cheaper syscalls on linux) do make a rather striking difference.
Generally running a mixed system is a pain because of the differing ABI causing a need for two versions of every library.
Well I'd be happy with a mysqlclient build that worked with whatever include files are being scooped up by gcc.
Tony Sidaway:
Is there some magic phrase I can tell configure that will make it realise I want to pick up the 32-bit /opt/mysql50/include/mysql include files, and not the include files that lives at /usr/sfw/include/mysql that it seems to prefer?
i have removed the mysql include files in /usr/sfw/ since they don't correspond to a useful client library.
k.
On 12/14/05, Kate lithiana@livejournal.com wrote:
i have removed the mysql include files in /usr/sfw/ since they don't correspond to a useful client library.
Oh, that clears up some confusion. I pointed the compiler at /opt/mysql50/include and it did have the effect of producing a fairly coherent 32-bit dbd library that knows its way around the database.
toolserver-l@lists.wikimedia.org