Darwin: make check fails with "child process exited with exit code 134" - Mailing list pgsql-bugs

From Matthias Schmitt
Subject Darwin: make check fails with "child process exited with exit code 134"
Date
Msg-id 5A871654-B250-4837-99DB-EB6D44E64E65@mmp.lu
Whole thread Raw
Responses Re: Darwin: make check fails with "child process exited with exit code 134"
List pgsql-bugs
Hello,

I am trying to compile PostgreSQL 9.3.1 on the new OS X Mavericks, which =
uses Darwin Kernel Version 13.0.0.

The compile process finishes fine, but when I am trying to test the =
resulting binary =93make check=94 fails with:

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D initializing database =
system           =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> pg_regress: initdb failed
> Examine /<my path>/postgresql-9.3.1/src/test/regress/log/initdb.log =
for the reason.


The =93initdb.log=94 file contains the following lines:

> creating directory /<my =
path>/postgresql-9.3.1/src/test/regress/./tmp_check/data ... ok
> creating subdirectories ... ok
> selecting default max_connections ... 100
> selecting default shared_buffers ... 128MB
> creating configuration files ... ok
> creating template1 database in /<my =
path>/postgresql-9.3.1/src/test/regress/./tmp_check/data/base/1 ... ok
> initializing pg_authid ... ok
> initializing dependencies ... ok
> creating system views ... ok
> loading system objects' descriptions ... ok
> creating collations ... ok
> creating conversions ... ok
> creating dictionaries ... ok
> setting privileges on built-in objects ... ok
> creating information schema ... sh: line 1: 54928 Abort trap: 6        =
   "<my path>/postgresql-9.3.1/src/test/regress/tmp_check/install/<my =
path>/pgsql/bin/postgres" --single -F -O -c search_path=3Dpg_catalog -c =
exit_on_error=3Dtrue -j template1 > /dev/null
> child process exited with exit code 134

I was trying to compile with the default clang compiler as good as with =
the gcc-4.2 compiler. Both result in the same error message. I searched =
the mailing lists. Some fixed their "code 134=94 problems on other =
operating systems by deleting and re-compiling the PostgreSQL code =
directories. I did this a few times, but the result was always the same.
Any ideas?

Thank you for your support

Greetings from Luxembourg

Matthias Schmitt

pgsql-bugs by date:

Previous
From: Vadim Yevsyukov
Date:
Subject: Re: BUG #8553: CRITICAL - delete from doesn't delete rows, select returns them anyway
Next
From: Andres Freund
Date:
Subject: Re: Darwin: make check fails with "child process exited with exit code 134"