Re: RE- Compile 7.1.3 on SCO OpenServer 5.0.6a

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Steve Burger <steve(at)customware(dot)aust(dot)com>, <pgsql-ports(at)postgresql(dot)org>
Subject: Re: RE- Compile 7.1.3 on SCO OpenServer 5.0.6a
Date: 2001-10-24 19:07:57
Message-ID: Pine.LNX.4.30.0110242103240.647-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-ports

Tom Lane writes:

> Peter Eisentraut <peter_e(at)gmx(dot)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(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Responses

Browse pgsql-ports by date

  From Date Subject
Next Message Lamar Owen 2001-10-24 22:04:14 Re: Which mx RPM do you have for postgresql-python?
Previous Message jvsyqbldd 2001-10-24 16:33:11 xmorylp ^ ccpenwk