Hi, 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.
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@parspro.com wrote:
Hi, 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.
-- -JT
On Thu, Mar 25, 2010 at 9:43 PM, John Toohey jt@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.
Yes, OpenDBX current: nil was the way to do it. I will add this to the website documentation. Sorry, I thought I have added a reset method, that does that..but no. Anyway, in next commit there will be.
Regarding the library, how did you install OpenDBX in your Linux machine ? compile and install ? using a binaries ? Because yes, you should have 3 things:
- libopendbx.so which is the "core" and generic code for opendbx - libpgsqlbackend.so which is one for each database (one in your case) - the postgres client libraries.
Did you see this link ? maybe it is of help
http://www.squeakdbx.org/Compiling%20for%20different%20backends/Common%20ste...
And this one:
http://www.squeakdbx.org/Compiling%20and%20installing%20OpenDBX
Cheers
Mariano
On Thu, Mar 25, 2010 at 16:20, John Toohey jt@parspro.com wrote:
Hi, 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.
-- -JT
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
On Thu, Mar 25, 2010 at 9:57 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Thu, Mar 25, 2010 at 9:43 PM, John Toohey jt@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.
Yes, OpenDBX current: nil was the way to do it. I will add this to the website documentation. Sorry, I thought I have added a reset method, that does that..but no. Anyway, in next commit there will be.
I just added OpenDBX reset and even more, this method is called when the image starts...so, it will be done automatically. If you start several times the image in the same OS that method will be called anyway. However, it just does a new of a single class....so, no problem ;)
Regarding the library, how did you install OpenDBX in your Linux machine ? compile and install ? using a binaries ? Because yes, you should have 3 things:
- libopendbx.so which is the "core" and generic code for opendbx
- libpgsqlbackend.so which is one for each database (one in your case)
- the postgres client libraries.
Did you see this link ? maybe it is of help
http://www.squeakdbx.org/Compiling%20for%20different%20backends/Common%20ste...
And this one:
http://www.squeakdbx.org/Compiling%20and%20installing%20OpenDBX
Cheers
Mariano
On Thu, Mar 25, 2010 at 16:20, John Toohey jt@parspro.com wrote:
Hi, 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.
-- -JT
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
Yep, found them, had set my lib path to /usr/local/opendbx/lib. However, now I have :- ioLoadModule(/usr/local/lib/libopendbx.so):
/usr/local/lib/libopendbx.so: wrong ELF class: ELFCLASS64
when I access the DB from Pharo. Seems to be a 64/32 issue, 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++ installed, and passing --disable-utils should be part of the docs. 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.
On Thu, Mar 25, 2010 at 16:43, John Toohey jt@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@parspro.com wrote:
Hi, 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.
-- -JT
-- -JT
I give up, this is the third time in as many months, I've tried OpenDBX. Has anyone here managed to get this to work on a 64bit Linux box, with a 32 bit VM? I've added CFLAGS=-m32 and CXXFLAGS=-m32, LDEMULATION=i385, and ./configure --build=i366, but I still get 64 bits drivers. (These are production servers, so I cannot change them to 32 bit)
Is there somewhere I can get pre-build 32 binaries that will work?
On Thu, Mar 25, 2010 at 20:36, John Toohey jt@parspro.com wrote:
Yep, found them, had set my lib path to /usr/local/opendbx/lib. However, now I have :- ioLoadModule(/usr/local/lib/libopendbx.so):
/usr/local/lib/libopendbx.so: wrong ELF class: ELFCLASS64
when I access the DB from Pharo. Seems to be a 64/32 issue, 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++ installed, and passing --disable-utils should be part of the docs. 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.
On Thu, Mar 25, 2010 at 16:43, John Toohey jt@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@parspro.com wrote:
Hi, 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.
-- -JT
-- -JT
-- -JT
On Fri, Mar 26, 2010 at 2:00 AM, John Toohey jt@parspro.com wrote:
I give up, this is the third time in as many months, I've tried OpenDBX. Has anyone here managed to get this to work on a 64bit Linux box, with a 32 bit VM?
I don't have a 64 bits machine, so I never tested. Esteban did it, and thus, I wrote his notes that time:
http://www.squeakdbx.org/news/SqueakDBX%20in%20Snow%20Leopard%2064%20bits
Hope this helps.
Cheers
Mariano
I've added CFLAGS=-m32 and CXXFLAGS=-m32, LDEMULATION=i385, and ./configure --build=i366, but I still get 64 bits drivers. (These are production servers, so I cannot change them to 32 bit)
Is there somewhere I can get pre-build 32 binaries that will work?
On Thu, Mar 25, 2010 at 20:36, John Toohey jt@parspro.com wrote:
Yep, found them, had set my lib path to /usr/local/opendbx/lib. However, now I have :- ioLoadModule(/usr/local/lib/libopendbx.so):
/usr/local/lib/libopendbx.so: wrong ELF class: ELFCLASS64
when I access the DB from Pharo. Seems to be a 64/32 issue, 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++ installed, and passing --disable-utils should be part of the docs. 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.
On Thu, Mar 25, 2010 at 16:43, John Toohey jt@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@parspro.com wrote:
Hi, 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.
-- -JT
-- -JT
-- -JT
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
I forgot to said that the 64 bits questions was also in the FAQ:
So I guess that you may already read it so it wouldn't help with the other link.
On Fri, Mar 26, 2010 at 4:50 AM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Fri, Mar 26, 2010 at 2:00 AM, John Toohey jt@parspro.com wrote:
I give up, this is the third time in as many months, I've tried OpenDBX. Has anyone here managed to get this to work on a 64bit Linux box, with a 32 bit VM?
I don't have a 64 bits machine, so I never tested. Esteban did it, and thus, I wrote his notes that time:
http://www.squeakdbx.org/news/SqueakDBX%20in%20Snow%20Leopard%2064%20bits
Hope this helps.
Cheers
Mariano
I've added CFLAGS=-m32 and CXXFLAGS=-m32, LDEMULATION=i385, and ./configure --build=i366, but I still get 64 bits drivers. (These are production servers, so I cannot change them to 32 bit)
Is there somewhere I can get pre-build 32 binaries that will work?
On Thu, Mar 25, 2010 at 20:36, John Toohey jt@parspro.com wrote:
Yep, found them, had set my lib path to /usr/local/opendbx/lib. However, now I have :- ioLoadModule(/usr/local/lib/libopendbx.so):
/usr/local/lib/libopendbx.so: wrong ELF class: ELFCLASS64
when I access the DB from Pharo. Seems to be a 64/32 issue, 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++ installed, and passing --disable-utils should be part of the docs. 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.
On Thu, Mar 25, 2010 at 16:43, John Toohey jt@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@parspro.com wrote:
Hi, 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.
-- -JT
-- -JT
-- -JT
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
Docs update
- This link bring me only to the main page, and also the link :-
http://www.assembla.com/spaces/Proyecto-Proyecto/documents/cW1J8Mx40r3Rq-eJe... gives an "invalid space" error.
I found the Snow Leopard link via the FAQ. Thanks.
On Fri, Mar 26, 2010 at 03:50, Mariano Martinez Peck marianopeck@gmail.comwrote:
On Fri, Mar 26, 2010 at 2:00 AM, John Toohey jt@parspro.com wrote:
I give up, this is the third time in as many months, I've tried OpenDBX. Has anyone here managed to get this to work on a 64bit Linux box, with a 32 bit VM?
I don't have a 64 bits machine, so I never tested. Esteban did it, and thus, I wrote his notes that time:
http://www.squeakdbx.org/news/SqueakDBX%20in%20Snow%20Leopard%2064%20bits
Hope this helps.
Cheers
Mariano
I've added CFLAGS=-m32 and CXXFLAGS=-m32, LDEMULATION=i385, and ./configure --build=i366, but I still get 64 bits drivers. (These are production servers, so I cannot change them to 32 bit)
Is there somewhere I can get pre-build 32 binaries that will work?
On Thu, Mar 25, 2010 at 20:36, John Toohey jt@parspro.com wrote:
Yep, found them, had set my lib path to /usr/local/opendbx/lib. However, now I have :- ioLoadModule(/usr/local/lib/libopendbx.so):
/usr/local/lib/libopendbx.so: wrong ELF class: ELFCLASS64
when I access the DB from Pharo. Seems to be a 64/32 issue, 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++ installed, and passing --disable-utils should be part of the docs. 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.
On Thu, Mar 25, 2010 at 16:43, John Toohey jt@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@parspro.com wrote:
Hi, 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.
-- -JT
-- -JT
-- -JT
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
On Fri, Mar 26, 2010 at 12:53 PM, John Toohey jt@parspro.com wrote:
Docs update
- This link bring me only to the main page,
weird...it works for me :(
and also the link :-
http://www.assembla.com/spaces/Proyecto-Proyecto/documents/cW1J8Mx40r3Rq-eJe... gives an "invalid space" error.
Thanks for reporting. This has to be updated as all the information in that pdf is the same we already put in
http://www.squeakdbx.org/Compiling%20for%20different%20backends
Ok...so...more things to update in the website for the weekend :(
I found the Snow Leopard link via the FAQ. Thanks.
Excellent.
Cheers
Mariano
On Fri, Mar 26, 2010 at 03:50, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Fri, Mar 26, 2010 at 2:00 AM, John Toohey jt@parspro.com wrote:
I give up, this is the third time in as many months, I've tried OpenDBX. Has anyone here managed to get this to work on a 64bit Linux box, with a 32 bit VM?
I don't have a 64 bits machine, so I never tested. Esteban did it, and thus, I wrote his notes that time:
http://www.squeakdbx.org/news/SqueakDBX%20in%20Snow%20Leopard%2064%20bits
Hope this helps.
Cheers
Mariano
I've added CFLAGS=-m32 and CXXFLAGS=-m32, LDEMULATION=i385, and ./configure --build=i366, but I still get 64 bits drivers. (These are production servers, so I cannot change them to 32 bit)
Is there somewhere I can get pre-build 32 binaries that will work?
On Thu, Mar 25, 2010 at 20:36, John Toohey jt@parspro.com wrote:
Yep, found them, had set my lib path to /usr/local/opendbx/lib. However, now I have :- ioLoadModule(/usr/local/lib/libopendbx.so):
/usr/local/lib/libopendbx.so: wrong ELF class: ELFCLASS64
when I access the DB from Pharo. Seems to be a 64/32 issue, 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++ installed, and passing --disable-utils should be part of the docs. 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.
On Thu, Mar 25, 2010 at 16:43, John Toohey jt@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@parspro.com wrote:
Hi, 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.
-- -JT
-- -JT
-- -JT
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
Thanks for the 32 bit libs, have them installed now, and they work, unfortunately the Postgres libs (libpq.so) is also 64 bit, so back to square one. Assuming that these are just for talking to the DB, I'm going to try to copy 32 bit versions of them, and see if they work.
On Fri, Mar 26, 2010 at 12:00, Mariano Martinez Peck marianopeck@gmail.comwrote:
On Fri, Mar 26, 2010 at 12:53 PM, John Toohey jt@parspro.com wrote:
Docs update
- This link bring me only to the main page,
weird...it works for me :(
and also the link :-
http://www.assembla.com/spaces/Proyecto-Proyecto/documents/cW1J8Mx40r3Rq-eJe... gives an "invalid space" error.
Thanks for reporting. This has to be updated as all the information in that pdf is the same we already put in
http://www.squeakdbx.org/Compiling%20for%20different%20backends
Ok...so...more things to update in the website for the weekend :(
I found the Snow Leopard link via the FAQ. Thanks.
Excellent.
Cheers
Mariano
On Fri, Mar 26, 2010 at 03:50, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Fri, Mar 26, 2010 at 2:00 AM, John Toohey jt@parspro.com wrote:
I give up, this is the third time in as many months, I've tried OpenDBX. Has anyone here managed to get this to work on a 64bit Linux box, with a 32 bit VM?
I don't have a 64 bits machine, so I never tested. Esteban did it, and thus, I wrote his notes that time:
http://www.squeakdbx.org/news/SqueakDBX%20in%20Snow%20Leopard%2064%20bits
Hope this helps.
Cheers
Mariano
I've added CFLAGS=-m32 and CXXFLAGS=-m32, LDEMULATION=i385, and ./configure --build=i366, but I still get 64 bits drivers. (These are production servers, so I cannot change them to 32 bit)
Is there somewhere I can get pre-build 32 binaries that will work?
On Thu, Mar 25, 2010 at 20:36, John Toohey jt@parspro.com wrote:
Yep, found them, had set my lib path to /usr/local/opendbx/lib. However, now I have :- ioLoadModule(/usr/local/lib/libopendbx.so):
/usr/local/lib/libopendbx.so: wrong ELF class: ELFCLASS64
when I access the DB from Pharo. Seems to be a 64/32 issue, 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++ installed, and passing --disable-utils should be part of the docs. 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.
On Thu, Mar 25, 2010 at 16:43, John Toohey jt@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@parspro.com wrote:
> Hi, > 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. > > -- > -JT > > >
-- -JT
-- -JT
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
Built the Postgres libs on a 32bit VMWare image, and copied them over. Everything seems to work now. I'm going to try to build a 64 bit VM, and FFI plugin, and test also.
For 32bit on a 64 bit kernel, I think the way to go is to build the 32bit static and dynamic libraries (Both Postgres and OpenDBX) on a 32bit VMWare image. Then create a lib32 directory under each /usr/local/lib and copy the files there. Add these paths to the front of the LD_LIBRARY_PATH in the script that starts the 32bit Pharo VM.
On Fri, Mar 26, 2010 at 12:42, John Toohey jt@parspro.com wrote:
Thanks for the 32 bit libs, have them installed now, and they work, unfortunately the Postgres libs (libpq.so) is also 64 bit, so back to square one. Assuming that these are just for talking to the DB, I'm going to try to copy 32 bit versions of them, and see if they work.
On Fri, Mar 26, 2010 at 12:00, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Fri, Mar 26, 2010 at 12:53 PM, John Toohey jt@parspro.com wrote:
Docs update
- This link bring me only to the main page,
weird...it works for me :(
and also the link :-
http://www.assembla.com/spaces/Proyecto-Proyecto/documents/cW1J8Mx40r3Rq-eJe... gives an "invalid space" error.
Thanks for reporting. This has to be updated as all the information in that pdf is the same we already put in
http://www.squeakdbx.org/Compiling%20for%20different%20backends
Ok...so...more things to update in the website for the weekend :(
I found the Snow Leopard link via the FAQ. Thanks.
Excellent.
Cheers
Mariano
On Fri, Mar 26, 2010 at 03:50, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Fri, Mar 26, 2010 at 2:00 AM, John Toohey jt@parspro.com wrote:
I give up, this is the third time in as many months, I've tried OpenDBX. Has anyone here managed to get this to work on a 64bit Linux box, with a 32 bit VM?
I don't have a 64 bits machine, so I never tested. Esteban did it, and thus, I wrote his notes that time:
http://www.squeakdbx.org/news/SqueakDBX%20in%20Snow%20Leopard%2064%20bits
Hope this helps.
Cheers
Mariano
I've added CFLAGS=-m32 and CXXFLAGS=-m32, LDEMULATION=i385, and ./configure --build=i366, but I still get 64 bits drivers. (These are production servers, so I cannot change them to 32 bit)
Is there somewhere I can get pre-build 32 binaries that will work?
On Thu, Mar 25, 2010 at 20:36, John Toohey jt@parspro.com wrote:
Yep, found them, had set my lib path to /usr/local/opendbx/lib. However, now I have :- ioLoadModule(/usr/local/lib/libopendbx.so):
/usr/local/lib/libopendbx.so: wrong ELF class: ELFCLASS64
when I access the DB from Pharo. Seems to be a 64/32 issue, 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++ installed, and passing --disable-utils should be part of the docs. 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.
On Thu, Mar 25, 2010 at 16:43, John Toohey jt@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@parspro.com wrote: > >> Hi, >> 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. >> >> -- >> -JT >> >> >> > > > -- > -JT > > >
-- -JT
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
-- -JT
John Toohey wrote:
I give up, this is the third time in as many months, I've tried OpenDBX. Has anyone here managed to get this to work on a 64bit Linux box, with a 32 bit VM? I've added CFLAGS=-m32 and CXXFLAGS=-m32, LDEMULATION=i385, and ./configure --build=i366, but I still get 64 bits drivers. (These are production servers, so I cannot change them to 32 bit)
Is there somewhere I can get pre-build 32 binaries that will work?
Could you get access to a 32-bit Linux OS installation, just so you can build the 32-bit libraries there, and then deploy them to your 64-bit machines? This strategy avoids the problem of having to get the cross-compiling options correct.
On Fri, Mar 26, 2010 at 11:36 AM, Yanni Chiu yanni@rogers.com wrote:
John Toohey wrote:
I give up, this is the third time in as many months, I've tried OpenDBX. Has anyone here managed to get this to work on a 64bit Linux box, with a 32 bit VM? I've added CFLAGS=-m32 and CXXFLAGS=-m32, LDEMULATION=i385, and ./configure --build=i366, but I still get 64 bits drivers. (These are production servers, so I cannot change them to 32 bit)
Is there somewhere I can get pre-build 32 binaries that will work?
Could you get access to a 32-bit Linux OS installation, just so you can build the 32-bit libraries there, and then deploy them to your 64-bit machines? This strategy avoids the problem of having to get the cross-compiling options correct.
I really don't know if that works or not. I am not an expert in such field. But just in case it works, I attach my 32 bits libraries compiled for OpenDBX and PostgreSQL. If this works, you should only have to uncompress and move the contents to /usr/lib
Cheers
Mariano
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
On Thu, Mar 25, 2010 at 9:36 PM, John Toohey jt@parspro.com wrote:
Yep, found them, had set my lib path to /usr/local/opendbx/lib. However, now I have :- ioLoadModule(/usr/local/lib/libopendbx.so):
/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++ installed,
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: http://www.squeakdbx.org/Compiling%20and%20installing%20OpenDBX 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
http://www.linuxnetworks.de/doc/index.php/OpenDBX/Setup/Common_problems
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:
http://www.squeakdbx.org/PostgreSQL%20for%20Win
And here:
http://www.linuxnetworks.de/doc/index.php/OpenDBX/Setup/Manual_builds#Withou...
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.
Cheers
Mariano
On Thu, Mar 25, 2010 at 16:43, John Toohey jt@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@parspro.com wrote:
Hi, 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.
-- -JT
-- -JT
-- -JT
SqueakDBX mailing list SqueakDBX@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
squeakdbx@lists.squeakfoundation.org
-
John Toohey -
Mariano Martinez Peck -
Yanni Chiu