Maybe a stupid question, but why not use the PostgresV2 ‘native’ driver. This one is network based, it needs no (annoying) libraries, just a socket connection ?
And it works perfectly with Glorp. Sven On 12 Dec 2013, at 13:29, Esteban A. Maringolo <emaring...@gmail.com> wrote: > Hi all, it is a 32bit Ubuntu 12.04 hosted in Digital Ocean. > > The image starts, but once I access something that needs to open a > GlorpSession I get that exception. > > I added a symlink from libpq.so to libpq.so.5.4, the other symlink was > already there. > > $ ls -l /usr/lib/libpq* > lrwxrwxrwx 1 root root 12 Dec 12 12:17 /usr/lib/libpq.so -> libpq.so.5.4 > lrwxrwxrwx 1 root root 12 Mar 6 2012 /usr/lib/libpq.so.5 -> libpq.so.5.4 > -rw-r--r-- 1 root root 163308 Mar 6 2012 /usr/lib/libpq.so.5.4 > > There is also a lot of libraries in /usr/lib/postgresql/9.1/ > > What is the expeced filename Pharo will look for? > > I'm not using the DBX driver, as far as I can tell, but the Native > Postgres driver instead. Which is non-sense given the fact it requires > de Glorp driver. I know. :-/ > > Esteban A. Maringolo > > > 2013/12/12 Guillermo Polito <guillermopol...@gmail.com>: >> Esteban, are you using dbxtalk? >> >> Either you use it or not, the VM will only find the external libraries if >> they are in a well known path (that is, for example /usr/lib/). If your >> libraries are in a different place, such as /usr/lib/i386blabla/ the VM >> library searching mechanism will not find it. >> >> Now, to fix that, you have many ways. I'd suggest not to change the PATH nor >> the LD_LIBRARY_PATH, cause you either change the library resolution for all >> the applications, or you change completely the resolution path for all the >> libraries the VM wants to load. The safest solution here, IMHO, is to add a >> symbolic link to the required library in the VM directory. >> >> And well, others already talked about the 32-64 bit thingy. >> >> cheers, >> Guille >> >> >> On Thu, Dec 12, 2013 at 9:34 AM, jtuc...@objektfabrik.de >> <jtuc...@objektfabrik.de> wrote: >>> >>> Esteban, >>> >>> sounds like you need to modify your PATH environment variable either >>> globally or in a startup bash script for your Pharo image. The directory >>> containing Postgres libs has to be in that PATH. >>> And, the other Esteban also asks about 32 or 64 bits, because it is very >>> likely you need to install a 32-bit driver if you are on a 64 Linux machine >>> (and even some additional libraries, apt-get install ia32-libs, iirc), >>> because Pharo doesn't support 64 bit libraries afaik. >>> >>> HTH >>> >>> Joachim >>> >>> Am 12.12.13 03:53, schrieb Esteban A. Maringolo: >>> >>>> Hi there, >>>> >>>> I'm moving my development server (Windows) into production (Ubuntu >>>> 12.04) and I'm facing some issues with, among other things, the >>>> PostgreSQL driver. >>>> >>>> I'm getting an: >>>> "Error: External module not found" >>>> >>>> My database login is as follows: >>>> >>>> sampleLogin >>>> ^Login new >>>> database: (PostgreSQLPlatform new characterEncoding: 'utf8'); >>>> username: 'user'; >>>> password: 'secret'; >>>> connectString: 'localhost_db'; >>>> encodingStrategy: (DBXStaticEncoding newForEncoding: #utf8). >>>> >>>> And then just a regular accessor for the previous login: >>>> >>>> DatabaseAccessor forLogin: self sampleLogin. >>>> >>>> >>>> How should I install the dependencies? >>>> >>>> I have a libpq.dll in my windows environment, and I already installed >>>> libpq5 drivers in the server (apt-get install libpq5) >>>> >>>> What else should I do? >>>> >>>> Regards, >>>> >>>> Esteban A. Maringolo >>>> >>>> >>> >>> >>> -- >>> ----------------------------------------------------------------------- >>> Objektfabrik Joachim Tuchel mailto:jtuc...@objektfabrik.de >>> Fliederweg 1 http://www.objektfabrik.de >>> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >>> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >>> >>> >> >
