Darwin: make check fails with "child process exited with exit code 134"

From: Matthias Schmitt <freak002(at)mmp(dot)lu>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Darwin: make check fails with "child process exited with exit code 134"
Date: 2013-10-28 14:21:46
Message-ID: 5A871654-B250-4837-99DB-EB6D44E64E65@mmp.lu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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 “make check” fails with:

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

The “initdb.log” 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=pg_catalog -c exit_on_error=true -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” 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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2013-10-28 14:42:25 Re: Darwin: make check fails with "child process exited with exit code 134"
Previous Message e.choneh 2013-10-28 14:13:07 BUG #8564: jdbc connexion still opened

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-10-28 14:30:22 Re: Document update in alter_foreign_data_wrapper.sgml
Previous Message Amit Kapila 2013-10-28 13:04:32 Re: ERROR : 'tuple concurrently updated'