r...@bb-c.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 t
Hello everybody,
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.
That's especially embarras
On Tue, Aug 8, 2017 at 12:36 PM, Tom Lane wrote:
> Hmmm ...
>
> > SHELL=/bin/tcsh
>
> Mine's bash ... I wonder whether that could make a difference here?
> I'm pretty sure the PG makefiles aren't set up for csh syntax.
> But I can't see how that would make it work in the manual case
> and not whe
r...@bb-c.de (Rainer J.H. Brandt) writes:
> Tom Lane writes:
>> 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
Tom Lane writes:
> r...@bb-c.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 i
r...@bb-c.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 h
Hi,
I'm coming back to an old thread. My original issue isn't resolved yet;
this is just to answer your questions below.
Adrian Klaver writes:
> [...]
> I do not build on OS X so this is a bit of a reach for me, still here it
> goes. From your original post the error was:
>
> "reating conversi
r...@bb-c.de (Rainer J.H. Brandt) writes:
> Tom Lane writes:
>> The whole thing's odd though --- certainly many people are building
>> PG successfully on macOS. There's got to be something unusual about
>> Rainer's build environment, but what?
> I thought so, too, but I'm beginning to doubt it.
On 07/04/2017 11:56 PM, Rainer J.H. Brandt wrote:
Tom Lane writes:
Adrian Klaver writes:
On 07/04/2017 01:29 PM, Rainer J.H. Brandt wrote:
Good to know. I removed those options and tried again.
Did you run make clean before re-running ./configure?
Personally I do "make distclean" before
Tom Lane writes:
> Adrian Klaver writes:
> > On 07/04/2017 01:29 PM, Rainer J.H. Brandt wrote:
> >> Good to know. I removed those options and tried again.
>
> > Did you run make clean before re-running ./configure?
>
> Personally I do "make distclean" before changing any configure options.
> I'
Adrian Klaver writes:
> On 07/04/2017 01:29 PM, Rainer J.H. Brandt wrote:
>> Good to know. I removed those options and tried again.
> Did you run make clean before re-running ./configure?
Personally I do "make distclean" before changing any configure options.
I'm not sure how much difference th
Adrian Klaver writes:
> On 07/04/2017 01:29 PM, Rainer J.H. Brandt wrote:
> > Tom Lane writes:
> >> r...@bb-c.de (Rainer J.H. Brandt) writes:
>
> >>
> >> This makes little sense to me. 64-bit builds have been the default on
> >> macOS for some time.
> > Good to know. I removed those options and
On 07/04/2017 01:29 PM, Rainer J.H. Brandt wrote:
Tom Lane writes:
r...@bb-c.de (Rainer J.H. Brandt) writes:
This makes little sense to me. 64-bit builds have been the default on
macOS for some time.
Good to know. I removed those options and tried again.
Did you run make clean before re
Tom Lane writes:
> r...@bb-c.de (Rainer J.H. Brandt) writes:
> > I got this initdb error for a 64bit-build on macOS El Capitan and Sierra:
>
> > creating conversions ... FATAL: could not load library
> > "/opt/bb/170704/lib/postgresql/ascii_and_mic.so":
> > dlopen(/opt/bb/170704/lib/postgresql/
r...@bb-c.de (Rainer J.H. Brandt) writes:
> I got this initdb error for a 64bit-build on macOS El Capitan and Sierra:
> creating conversions ... FATAL: could not load library
> "/opt/bb/170704/lib/postgresql/ascii_and_mic.so":
> dlopen(/opt/bb/170704/lib/postgresql/ascii_and_mic.so, 10): Symbol
Hi,
I got this initdb error for a 64bit-build on macOS El Capitan and Sierra:
initdb -D /data/pg/hawk -E UTF8 --locale=C"
The files belonging to this database system will be owned by user "rjhb".
This user must also own the server process.
The database cluster will be initialized with locale "C"
16 matches
Mail list logo
