'function unavailable' when calling OpenDBXDriver for MySQL

I've used the instructions defined on the "http://dbxtalk.smallworks.eu/" website to setup the  OpenDBXDriver for a MySQL database. When I try to make a connection to the database, I'm getting the "function unavailable".  

I have this working on a Ubuntu 14.04 32bit OS.  I'm wondering if my problem is my 64bit Ubuntu or do I have other problems.


My setup:

    Ubuntu 14.04 64bit.
    Pharo 3.0
    libopendbx.so.1.2.0   i386 version

Brad Selfridge

It looks like eveything is there. This configuration looks almost identical to my 32os machine.  


root@brads-linux-laptop:/usr/lib# ldd libopendbx.so.1.2.0
        linux-gate.so.1 =>  (0xf76df000)
        libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf76b8000)
        libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7508000)
        /lib/ld-linux.so.2 (0xf76e0000)
root@brads-linux-laptop:/usr/lib#

Hi Brad,

You don't tell us if your MySQL is 32 bit?

Stephan

Hi Brad,

You don't tell us if your MySQL is 32 bit?

Stephan

---

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/function-unavailable-when-calling-OpenDBXDriver-for-MySQL-tp4790564p4790646.html

To unsubscribe from 'function unavailable' when calling OpenDBXDriver for MySQL, click here.
NAML

My database is 64 bit on my 64bit Ubuntu machine.

However, on my 32bit Ubuntu 14.04 machine, I have a 64 debian VM running that has a 64bit MySQL running which I can access just fine from 32bit host machine running Pharo.

Hello Brad,

On 2014-11-17 17:34, [hidden email] wrote:
> My database is 64 bit on my 64bit Ubuntu machine.
>
> However, on my 32bit Ubuntu 14.04 machine, I have a 64 debian VM
> running
> that has a 64bit MySQL running which I can access just fine from 32bit
> host
> machine running Pharo.

I would guess that the 32 Bit MySQL client libraries are not installed.
Please check if you have libmysqlclient:i386 and libopendbx:i386 (or
what the proper name is, I'm not on an ubuntu machine right now)
installed.

dpkg -l | grep mysql | awk ' { print $2 } '
dpkg -l | grep dbx | awk ' { print $2 } '

The "libmysqlclient18:amd64" looks suspicious.

brad@brads-linux-laptop:~$ sudo dpkg -l | grep mysql | awk ' { print $2 } '
libdbd-mysql-perl
libmysqlclient18:amd64
libmysqlclient18:i386
libmysqlcppconn7
libopendbx1-mysql
libqt4-sql-mysql:i386
mysql-client
mysql-client-5.5
mysql-client-core-5.5
mysql-common
mysql-server
mysql-server-5.5
mysql-server-core-5.5
mysql-utilities
mysql-workbench
mysql-workbench-data
python-mysql.connector
brad@brads-linux-laptop:~$

brad@brads-linux-laptop:~$ sudo dpkg -l | grep dbx | awk ' { print $2 } '
libopendbx1
libopendbx1-mysql
brad@brads-linux-laptop:~$

Hello Brad,

as far as I can tell, you have the 32 bit mysql client libraries
installed (don't worry, the 64 and 32 bit version can coexist) - but I
am not sure about opendbx.

Please try

sudo apt-get install libopendbx1:i386 libopendbx1-mysql:i386

Best regards,
   Markus

On 11/17/2014 11:37 AM, Markus Fritsche wrote:
> sudo apt-get install libopendbx1:i386 libopendbx1-mysql:i386


brad@brads-linux-laptop:~$ sudo apt-get install libopendbx1:i386
libopendbx1-mysql:i386 [sudo] password for brad:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libopendbx1:i386 is already the newest version.
libopendbx1:i386 set to manually installed.
libopendbx1-mysql:i386 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
brad@brads-linux-laptop:~$

Hi,

So as far as I can see, you have all dependencies...

I remember that I had to reinitialize the OpenDBX libraries to change
the adaptor to the native library calls (from FFI to NBPharoOpenDBX or
similar). Unfortuanetly, I don't have the image at hand.

How would one re-initialize OpenDBX libraries?

Brad Selfridge
913-269-2385

I think it's "(Smalltalk at: #NBPharoOpenDBX) installAsCurrent.

Brad Selfridge
913-269-2385

On 2014-11-17 23:14, Brad wrote:
> I think it's "(Smalltalk at: #NBPharoOpenDBX) installAsCurrent.

That sounds familiar. But since I didn't read a "hooray", I guess that
didn't do the trick either?

Off for some sleep