Re: RE- Compile 7.1.3 on SCO OpenServer 5.0.6a

Just to recap I'm currently compiling with the following lines added to
Makefile.shlib

> ifeq ($(PORTNAME), sco)
>   shlib := lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_
> VERSION)
>   LINK.shared = $(COMPILER) -G -Kpic -belf
> endif
>
postmaster and psql seem to work ok. but libpgtcl.so dies with the following

couldn't load file "/usr/local/pgsql/lib/libpgtcl.so": dynamic linker :
/usr/local/bin/bltwish : error opening libpq.so

Figuring this looks like a pathing issue so I

ln /usr/local/pgsql/lib/libpq.so /usr/lib

and the error changes to
couldn't load file "/usr/local/pgsql/lib/libpgtcl.so": dynamic linker:
/usr/local/bin/bltwish: relocation error: symbol not found: crypt

It would be great to get this working.

Regards Steve Burger

Peter Eisentraut wrote:

> Tom Lane writes:
>
> > Peter Eisentraut <peter_e@gmx.net> writes:
> > > You should configure --disable-shared because shared libraries aren't
> > > supported on SCO yet.
> >
> > If that's the answer, meseems it should be mentioned in doc/FAQ_SCO.
> > Or even enforced in template/sco.  But since neither is the case,
> > I wonder whether the previous users of the SCO port haven't managed
> > to make it work.
>
> The current Makefile.shlib will fail in the install target if the platform
> has no shared library support.  This is a bug because Makefile.shlib
> should provide transparent library building.  However, it might have been
> that the installation would silently proceed if the local version of
> 'install' was sufficiently ill-behaved.  But we don't use that anymore.
>
> In any case, the 7.2 release will have shared library support on SCO (at
> least theoretically), and I'll make sure that Makefile.shlib gets fixed.
>
> --
> Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly