[SqueakDBX] Re: Problem deploying image from OSX to Linux
Mariano Martinez Peck
marianopeck at gmail.com
Fri Mar 26 07:59:21 UTC 2010
On Thu, Mar 25, 2010 at 9:36 PM, John Toohey <jt at parspro.com> wrote:
> Yep, found them, had set my lib path to /usr/local/opendbx/lib. However,
> now I have :-
> /usr/local/lib/libopendbx.so: wrong ELF class: ELFCLASS64
> when I access the DB from Pharo. Seems to be a 64/32 issue,
yes, it is about that.
> but adding CFLAGS="-m32" to my env, and then doing ./configure, give me an
> error that the compiler cannot create an executable.
> I'm writing all this down, as some issues, like the requirement to have g++
This is actually not true. It depends how you are installing OpenDBX. If you
want to compile, then of course it is needed. But you can use OpenDBX
binaries files instead. In Windows you can use directly the dlls and in
Linux you can use the .deb or .rpm as it is explained here:
I don't know how to do it in MacOS, thus.
> and passing --disable-utils should be part of the docs.
We consider that --disable-utils is not a SqueakDBX problem, but OpenDBX.
And that's why ( I did it myself ) added
For the moment, I only found this problem in Windows, and hence it is
explained in the Windows compiling:
Look for example for PostgreSQL in Windows:
Now...what would be great is to make it by default disable. I will ask this
to OpenDBX author.
> Maybe when I am done, and all tests are green, I can write up OSX and Linux
> with Pharo RC3 as a FAQ. Most of this is available on the site, but
> some specific examples might help people also.
Yes, please! we will really appreciate that.
> On Thu, Mar 25, 2010 at 16:43, John Toohey <jt at parspro.com> wrote:
>> I set OpenDBX current: nil, and now it uses the Linux driver, but have the
>> Unable to FInd Function Address error. According to the docs, the library
>> should be called libopendbx.so, but after building and installing on my
>> system, I have libpgsqlbackend.so, and no file called libopendbx.so.
>> On Thu, Mar 25, 2010 at 16:20, John Toohey <jt at parspro.com> wrote:
>>> I just deployed my test image, after testing on OSX, to a Linux
>>> production server, but the DBX drivers still think they are on OSX. In
>>> #createConnection, OpenDBX current returns the OSX driver. What is the best
>>> way to reset this, and can I do it in a running image.
> SqueakDBX mailing list
> SqueakDBX at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SqueakDBX