Bug 112244 - Makefile.port for building C extension functions is missing
Summary: Makefile.port for building C extension functions is missing
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: postgresql
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tom Lane
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-16 16:38 UTC by andrew
Modified: 2013-07-03 02:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-01-14 20:15:49 UTC
Embargoed:


Attachments (Terms of Use)

Description andrew 2003-12-16 16:38:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5)
Gecko/20031007

Description of problem:
If you try to build any of the sample extension DLLs in
/usr/share/doc/postgresql-docs-7.3.4/tutorial (or try to make your own
functions), you need to include /usr/include/pgsql/Makefile.global to
set up the PG build environment in your Makefile.

However, Makefile.global needs to include
$(top_builddir)/src/Makefile.port to set platform-specific build options.

Unfortunately, "Makefile.port" is (a) not included in the RPM, and (b)
is hard-coded to reside in the "src" directory (see Makefile.global).


Version-Release number of selected component (if applicable):
7.3.4-3.rhl9

How reproducible:
Always

Steps to Reproduce:
See description.

Actual Results:  Cannot build shared object server extensions.

Expected Results:  Should be able to build 'em.

Additional info:

Comment 1 Tom Lane 2004-02-26 00:34:05 UTC
We can certainly include Makefile.port in the RPM, but I don't think
that gets the job done --- the tutorial Makefile is designed for
building in a normal build tree, as is Makefile.global itself.
There doesn't seem to be any easy way to use these makefiles in
building modules after-the-fact using files installed where the
RPMs put them.  I think I'll have to punt on this for the moment,
and consult Lamar Owen and some other people about what to do.

Comment 2 Tom Lane 2005-01-14 20:15:49 UTC
This is fixed (finally) in PostgreSQL 8.0, which we should have in
Fedora Core 4.


Note You need to log in before you can comment on or make changes to this bug.