From: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
---|---|
To: | Trond Eivind Glomsrød <teg(at)redhat(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PgSQL-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Pl/Tcl problem |
Date: | 2001-12-15 15:58:23 |
Message-ID: | Pine.LNX.4.33L2.0112151254240.633-100000@aguila.protecne.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, 15 Dec 2001, Trond Eivind Glomsrød wrote:
> On Sat, 15 Dec 2001, Tom Lane wrote:
>
> > teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> > > Nah, the problem is that the module is created like this:
> > > gcc -pipe -shared -Wl,-soname,libtcl.so.0 -o pltcl.so pltcl.o -L/usr/lib -ltcl -ldl -lieee -lm -lc
> > > The pltcl.so module thus has soname libtcl.so.0. That leads to
> > > problems, as the same soname is used by the tcl library.
> >
> > Ugh. Is this our fault, or Tcl's?
>
> I'm not sure. One thing which probably affects it, is that we have a
> proper soname for libtcl (in addition to the nonstandard library name),
> which we're trying to upstream. What I'm not sure of is where soname for
> the postgresql tcl module comes from - "libtcl.so.0" is not a sane one to
> use.
I'd say it's the RPM packaging, for my problem was solved as soon as I
used the source version of pltcl.so without touching Tcl or anything
else. Can't prove that though.
--
Alvaro Herrera (<alvherre[(at)]atentus(dot)com>)
"Los romanticos son seres que mueren de deseos de vida"
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-12-15 17:13:41 | Re: Pl/Tcl problem |
Previous Message | Trond Eivind Glomsrød | 2001-12-15 14:19:04 | Re: Pl/Tcl problem |