Re: 64bit initdb failure on macOS 10.11 and 10.12

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: rjhb(at)bb-c(dot)de (Rainer J(dot)H(dot) Brandt)
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: 64bit initdb failure on macOS 10.11 and 10.12
Date: 2017-08-09 14:04:26
Message-ID: 23358.1502287466@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

rjhb(at)bb-c(dot)de (Rainer J.H. Brandt) writes:
> I have found my mistake. I apologize for not telling the whole truth
> about my build process. The answer is what it had to be: There was one
> step I had forgotten about: My build script stripped all binaries, i.e.
> it ran /usr/bin/strip on all of them.

Hah ... so then there wasn't anything specific to
check_encoding_conversion_args, that just happened to be the first symbol
the dynamic linker tried to look up.

I see that Apple's version of strip(1) has an option to supply a file
listing symbols to be kept. So if we had an authoritative list of the
symbols meant to be exported from core Postgres to extensions, you could
use that to filter out unnecessary symbols. Unfortunately, no such
list has ever been prepared :-(

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Colin 't Hart 2017-08-09 14:42:37 How to ALTER EXTENSION name OWNER TO new_owner ?
Previous Message Harry Ambrose 2017-08-09 13:40:04 Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100