BUG #1077: install-strip does not work for MacOS X 10.2.8

The following bug has been logged online:

Bug reference:      1077
Logged by:          Andrew MacRae

Email address:      Andrew.MacRae@smu.ca

PostgreSQL version: 7.5 Dev

Operating system:   MacOS X 10.2.8

Description:        install-strip does not work for MacOS X 10.2.8

Details:


MacOS X 10.2.8, v.7.4.1 of postgreSQL, configure options: ./configure
--with-openssl --with-perl --with-java

The compile proceeds uneventfully and successfully.  Upon installation step
("make install-strip"), it also generates no errors.  However, during the
database initialization (after making the data directory, setting the
appropriate owner, and su to the "postgres" user), the database initdb
command generates the following error message:

============
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
The files belonging to this database system will be owned by user
"postgres".
This user must also own the server process.

The database cluster will be initialized with locale C.

fixing permissions on existing directory /usr/local/pgsql/data... ok
creating directory /usr/local/pgsql/data/base... ok
creating directory /usr/local/pgsql/data/global... ok
creating directory /usr/local/pgsql/data/pg_xlog... ok
creating directory /usr/local/pgsql/data/pg_clog... ok
selecting default max_connections... 50
selecting default shared_buffers... 300
creating configuration files... ok
creating template1 database in /usr/local/pgsql/data/base/1... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ok
creating conversions... ERROR:  could not load library
"/usr/local/pgsql/lib/ascii_and_mic.so": dyld: /usr/local/pgsql/bin/postgres
Undefined symbols:
        /usr/local/pgsql/lib/ascii_and_mic.so undefined reference to
_pg_ascii2mic expected to be defined in the executable
        /usr/local/pgsql/lib/ascii_and_mic.so undefined reference to
_pg_mic2ascii expected to be defined in the executable
============

If the plain "make install" installation step is used instead (i.e. without
any stripping), then the same initdb command succeeds with no errors, and
everything works as expected.

I have encountered some problems with dynamic libraries on MacOS X before
when stripping them.  Some of the default options are okay for most binaries
but apparently strip "too much" for a shared library, so the options have to
be more carefully specified if one is being made.  This could be the problem
here.  I'm sorry to be vague about this, but I do not know enough about the
operation of dynamic/shared libraries on MacOS X to offer a more specific
solution.