Skip site navigation (1) Skip section navigation (2)

Re: PL compilations ignores LDFLAGS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL compilations ignores LDFLAGS
Date: 2009-04-23 18:47:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> I supposed to do something like this for libpq, libpgtypes and so on.

> *** pgsql.orig.d976d4abedca/src/interfaces/libpq/Makefile	2009-04-23 20:07:21.178749132 +0200
> --- pgsql.orig/src/interfaces/libpq/Makefile	2009-04-23 20:07:21.194173674 +0200
> ***************
> *** 65,70 ****
> --- 65,71 ----
>   endif
>   SHLIB_EXPORTS = exports.txt
> + rpath = ""
>   all: all-lib

That seems like a pretty awful idea.  How do you know that the rpath
isn't being used to pick up stuff like openssl?

> For I suggest to use path to which can be detect in configure.

I believe that we expect to get any required switches for that out of
the TCL_LIB_SPEC and/or TCL_LIBS variables, which we get from tclconfig.
I wonder if you are working with an improperly configured Tcl

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2009-04-23 18:50:47
Subject: Re: Why do we let CREATE DATABASE reassign encoding?
Previous:From: Bill MoranDate: 2009-04-23 18:46:49
Subject: Re: Why do we let CREATE DATABASE reassign encoding?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group