| 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-08 15:14:19 |
| Message-ID: | 3311.1502205259@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:
> This 32/64 business isn't the problem, though.
> I've found out that everything works if I type the configure/make commands
> in my shell (which isn't what I said before, sorry about that), but stops
> working if I put them into a Perl script (which is how I automate things
> across OSes).
Ooooh, that's interesting ...
> The weird thing is that the commands are absolutely the same,
> and environment is the same, too.
I bet not. We've seen problems with macOS unexpectedly deciding to
filter away inherited environment variables in some situations.
It might be useful to put "env >somefile" into the PG makefile and
compare results between the two ways of invoking it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rainer J.H. Brandt | 2017-08-08 16:27:06 | Re: 64bit initdb failure on macOS 10.11 and 10.12 |
| Previous Message | Rainer J.H. Brandt | 2017-08-08 15:04:03 | Re: 64bit initdb failure on macOS 10.11 and 10.12 |