I'm still filling gaps in my Linux juju kit, and in this case learned that one uses the file command to discover the nature of a binary. Libodbc.so tuns out to be symbolic link to a 64 bit binary. unixodbc.org (under manuals aka /doc) has a document on changes for 64 bits. I do not yet vouch for its correctness, but they have me fooled so far :) Could some kind FFI guru give me an idea of what ugliness might await me? Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Thursday, September 03, 2009 6:34 PM To: Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] FFI meets 74 bits - there be dragons here?? Hello all, So far, I am one for two on getting ODBC to work on my 64 bit Ubuntu system. I'm using a pre-production (the only option we were given by our IT guys) Cisco vpn that does not support 64 bit systems; enter a 32 bit vpn and some copied libraries. After that fun, I have been able to get isql (unixODBC test utility) to see a MySQL server I have living on a blade machine. That much works. My Pharo image seems unable to talk to it, and I am wondering whether it might be because the library is 64 bit - please excuse me if that's just plain stupid. Of course, so was installing the 64 bit OS<g>, but I figure there will not be an option some day, so I'm trying to get my bad news early. Any ideas about how to proceed? I'm thinking of subclassing ODBCLibrary and tweaking the types (something on the net addresses some changes) to see if I can get some success and then keep going as needed. Does that sound reasonable? Any better ideas? FreeTDS is letting me down talking to a SQL server machine. If anyone has set that up successfully, I would greatly enjoy knowing what you did. Bill _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project