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" <[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 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.
Well, both the PL languages and the character set conversion support are *only* buildable as shared libraries right now. If you want to statically link those into the main backend build, you can probably do it, but it will take some nontrivial hacking.
In the meantime it would appear that your linker ignores the -E (export all symbols) switch when -static is specified. I suppose it thinks that not only don't you want any shared libraries now, but you won't want any dynamically loaded libraries later. This is a Bad Idea; complain to the linker hackers about it.
regards, tom lane
---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
