6 messages in com.mysql.lists.plusplusRe: Do we need to recompile MySQL++ l...
FromSent OnAttachments
Ankur G35 Saxena25 Jul 2006 09:57 
Ankur G35 Saxena25 Jul 2006 10:18 
Carlos Flores25 Jul 2006 10:20 
Carlos Flores25 Jul 2006 10:31 
Ankur G35 Saxena25 Jul 2006 10:42 
Ovidiu Bivolaru25 Jul 2006 10:52 
Subject:Re: Do we need to recompile MySQL++ lib for Xeon 64bit / Dual Core
From:Carlos Flores (caf@gmail.com)
Date:07/25/2006 10:20:44 AM
List:com.mysql.lists.plusplus

Dear Ankur

Yes, i think you will need to rebuild, because amd64 and Intel noncona (known as x86_64) are a different binary platform if the os and or the code was compiled with any optimization like the -march=someprocessor flag, but the weird thing seems to happen with your executable, you should try recompiling it for x86_64.

Myself I own one of those Sempron processors with a Venice Core, so it is x86_64, and i use ubuntu, sometimes code compiled for normal 32 bit processor does not work as desired because of the little different binary compatibility between the code.

2006/7/25, Ankur G35 Saxena <g35r@gmail.com>:

Hi, I have trouble trying to deal with a client in india who only has a xeon processor or a dual core and my application uses MySQL++ library to make the connection to mysql. The MySQL installation is a regular rpm file nothing specific for the 64 bit and i can run it just fine, but when my application runs on the xeon / dual core it core dumps at the time when i am trying to connect to mysql, connect() throws an exception, unfortunately the executable i sent to client didnt have a catch in it, so i dont know what seems to be the exact reason, but someone ever face this issue?

I can run the exact same code here in my lab with a regular P4.

What gives?