Re: [SQL] Build issues: -static builds resulting initdb problems

2005-05-06 Thread Metin Ozisik
, that will be much appreciated. Regards, -metin - Original Message - From: Tom Lane [EMAIL PROTECTED] To: Metin Ozisik [EMAIL PROTECTED] Cc: pgsql-sql@postgresql.org Sent: Saturday, April 30, 2005 9:03 AM Subject: Re: [SQL] Build issues: -static builds resulting initdb problems Metin Ozisik

Re: [SQL] Build issues: -static builds resulting initdb problems

2005-05-06 Thread Metin Ozisik
: Re: [SQL] Build issues: -static builds resulting initdb problems Metin Ozisik [EMAIL PROTECTED] 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

Re: [SQL] Build issues: -static builds resulting initdb problems

2005-04-30 Thread Tom Lane
Metin Ozisik [EMAIL PROTECTED] writes: 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

[SQL] Build issues: -static builds resulting initdb problems

2005-04-29 Thread Metin Ozisik
Version: 8.0.2 Platforms: Linux, Fedora Core 2, Suse 9.2, Mandrake 10.1 Build time parameter: CFLAGS="-static" ./configure results in a staticly linked binaries. (you are supposed to have static lib versions of readline, ncurses, etc, etc. of course) However, conversion shared objects

Re: [SQL] Build issues: -static builds resulting initdb problems

2005-04-29 Thread Tom Lane
Metin Ozisik [EMAIL PROTECTED] 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