Re: clsql-sys:database-type-load-foreign
Petter Gustad <[email protected]>
| Newsgroups | gmane.lisp.clsql.devel |
|---|---|
| Message-ID | <[email protected]> |
From: Kevin Rosenberg <kevin-HJRc7zDS/[email protected]> Subject: Re: [CLSQL-Devel] clsql-sys:database-type-load-foreign Date: Tue, 8 Jun 2004 10:19:03 -0600 > Petter Gustad wrote: > > No they are not linked. As I showed in my previous message "Red Hat > > Linux release 9 (Shrike)" and "SuSE SLES-8 (AMD64) VERSION = 8.1" does > > not have libpq.so. The older releases do have libpq.so linked to the > > latest version. > > I'd not familiar with those two specific versions. But, for Debian and > SuSE Pro AMD64 9.1, the symbol links are in the -devel packages. As I showed in my initial message the links are present in several other releases, but no in the ones mentioned above. > I suspect on your systems you have not installed the -devel packages > for PostgreSQL. Using the distribution's mysql libraries, by the way, > will require the mysql-devel packages as well. Well, I just installed the Red Hat CD where I checked off database support (or postgresql explicitly). ClSQL works fine if I just apply the patch to get the right filename. > Every Linux distribution I've seen have the so.n files in the library > package and the .so symbolic links in the library-devel packages. If They have been present in most Linux distributions I've seen too, but not in the two I mentioned above. > you look, my suspicion is that the proper symbolic link library names > are included in those packages in your distributions. Extreme [[email protected] lisp]$ rpm -qf /usr/lib/libpq.so error: file /usr/lib/libpq.so: No such file or directory [[email protected] lisp]$ rpm -qf /usr/lib/libpq.so.3 postgresql-libs-7.3.2-3 I only have two partitions on this disk / and /boot: [[email protected] root]# find / /boot -name libpq*so* /usr/lib/libpq.so.3 /usr/lib/libpq.so.3.0 Of course it could be that something went wrong during the installation. > I think adding a note that the packages with the development library > symbolic links are required makes sense. OK. I was just wanted to propose the patch to prevent others to run into this problem with the same distribution. No problem for me, I have root access and can generate the links myself or patch the given method. Petter