From: Metin Ozisik <metin@evincetek.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Build issues: "-static" builds resulting initdb problems
Date: Sat, 30 Apr 2005 00:04:36 -0700
Message-ID: <004301c54d52$f0ea4870$3401a8c0@pengu> (raw)
References: <003a01c549e4$1485eea0$3401a8c0@pengu>
<28245.1114835916@sss.pgh.pa.us>
The purpose of using static linking is to reduce dependencies to
shared-libraries (dependencies to different types and versions of Linux), so
an instance of postgreSQL, say built on Suse 9.0, would still work on
Mandrake 10.1. Yes it gets a bit bulky and have a number of disadvantages
over dynamic linking (on the plus side it would be a bit faster), however
the main motivater is binary portability.
Regards,
-metin
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Metin Ozisik" <metin@evincetek.com>
Cc: <pgsql-sql@postgresql.org>
Sent: Friday, April 29, 2005 9:38 PM
Subject: Re: [SQL] Build issues: "-static" builds resulting initdb problems
> "Metin Ozisik" <metin@evincetek.com> writes:
>> Build time parameter: CFLAGS="-static" ./configure
>
> Is there a particular reason for you to be doing that?
>
>> creating conversions ... FATAL: could not load library =
>> "../ascii_and_misc.so": ../../ascii_and_misc.so: undefined symbol: =
>> pg_mic2ascii
>
> pg_mic2ascii is a function exported by the core backend. I suppose
> that "-static" is somehow suppressing the visibility of that symbol
> to the dynamically loaded library ascii_and_misc.so. I am not sure
> whether this indicates a dynamic loader bug, or whether it's a case
> of "so don't do that then" ... but in any case I don't think it's
> a Postgres bug.
>
> regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: metin@evincetek.com, tgl@sss.pgh.pa.us
Subject: Re: Build issues: "-static" builds resulting initdb problems
In-Reply-To: <004301c54d52$f0ea4870$3401a8c0@pengu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox