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

From Matthias Schmitt
Subject Re: Darwin: make check fails with "child process exited with exit code 134"
Date
Msg-id 8C0FF1C0-5469-4FBB-9EC8-18D2BBB8430C@mmp.lu
Whole thread Raw
In response to Re: Darwin: make check fails with "child process exited with exit code 134"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 28.10.2013, at 17:39, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Well, I have
>=20
> CC =3D gcc
>=20
> which is what configure will pick by default, but I see
>=20
> $ gcc -v
> Configured with: =
--prefix=3D/Applications/Xcode.app/Contents/Developer/usr =
--with-gxx-include-dir=3D/Applications/Xcode.app/Contents/Developer/Platfo=
rms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1
> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
> Target: x86_64-apple-darwin13.0.0
> Thread model: posix
>=20
> so it's some variant of LLVM/clang.  In any case, Matthias claimed it
> didn't make a difference which compiler he picked, and I'm pushing
> back on that assertion.

There is a difference between=20

gcc

which starts clang and=20

/usr/bin/gcc-4.2

which is the real GCC version 4.2.1.

Regards

Matthias

pgsql-bugs by date:

Previous
From: Matthias Schmitt
Date:
Subject: Re: Darwin: make check fails with "child process exited with exit code 134"
Next
From: Andres Freund
Date:
Subject: Re: Darwin: make check fails with "child process exited with exit code 134"