Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.3/8.9.3) with ESMTP id LAA42668
	for <pgsql-interfaces@postgreSQL.org>;
	Wed, 30 Jun 1999 11:05:20 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA22258;
	Wed, 30 Jun 1999 11:03:58 -0400 (EDT)
To: "Ken J. Wright" <ken@ori-ind.com>
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] lo_export & pgaccess 
In-reply-to: Your message of Wed, 30 Jun 1999 07:44:47 -0700
	<3.0.1.32.19990630074447.00af73e0@ori-ind.com>
Date: Wed, 30 Jun 1999 11:03:57 -0400
Message-ID: <22256.930755037@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Ken J. Wright" <ken@ori-ind.com> writes:
> But...... this crypt problem
> has been hanging around for some time. And I do wonder why it can't just be
> a permanent entry in the *linux* section of Makefile.shlib?

That's not the right fix because it's not a Linux-only problem.  The
appropriate fix is in place elsewhere (and, hopefully, will actually
work as intended in 6.5.1 ;-)).

> Hold on a sec..... YES.
> Using the distribution make files, all that has to change (for Linux
> anyway) is to add -lcrypt to SHLIB_LINK in Makefile.shlib and have the
> extra sym links created. I just did this and all went well.

Great!  I'll fix the build rule to create those symlinks and then maybe
things will start to work properly...

			regards, tom lane