Ok, back to it now.....
I have always had to add the -crypt info to Makefile.shlib because I also
use libpq in other projects. I don't believe this is a crypt problem,
because ldd for libpgtcl.so shows the dependency on libcrypt.so.1. pgaccess
will run with the old libpgtcl.so.1 library accept for some new status
features that cause it to bomb. But I have yet to be successful with 6.4 or
6.5. 6.4 fails to load libpgtcl.so because of undefined symbol
"pgresStatus", and 6.5 fails because of undefined symbol "lo_export". I
have these problems on various RedHat 5.2 & 6.0 machines, so it is not
specific to one box.
Wait, hold on... I just did "ldd libpgtcl.so" on a working 6.4 box & it
shows a dependency on libpq.so.1. This seems normal! So why does my present
(failing) libpgtcl not have a dependency on libpq built in!!??.
Ken
At 14:02 06/28/1999 +0000, you wrote:
>Tom Lane wrote:
>>
>> "Ken J. Wright" <ken@ori-ind.com> writes:
>> > It fails with or without the symbolic link, as it's finding it's way
to the
>> > same libpgtcl.so ok. I'm thinking there must be something wrong with the
>> > build, but I'm not sure where to look. Are there other options besides
>> > --with-tcl that are required?
>>
>> Try adding -lcrypt to SHLIB_LINK in src/interfaces/libpgtcl/Makefile.in
>> (or .../Makefile if you already configured). There is code in there
>> that is supposed to do that for you, but it is broken in the 6.5 release
>> due to a silly oversight :-(
>
>I am sorry to say, noone to blame, but that piece of code that is
>supposed to do that didn't worked either in 6.4.x or in 6.5 beta x.
>As I recall, I checked every version against lcrypt including in linking
>but no version worked fine (at least for my RedHat 5.x servers).
>
>But it ain't such a big problem. As Tom said, just adding -lcrypt to
>SHLIB_LINK solve the problem.
>PostgreSQL 6.5 is such a great thing so you can pass over those minor
>problems!
>
>--
>Constantin Teodorescu
>FLEX Consulting Braila, ROMANIA
>
