Re: GCC vs clang - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: GCC vs clang
Date
Msg-id 4e4f5cc5f660987390b4cdc3fc78c99a@biglumber.com
Whole thread Raw
In response to Re: GCC vs clang  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: GCC vs clang
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Tom asked:
> What happens to plperl?

It still doesn't work. I was going to leave it out via --without-perl, 
and save fixing that for another day. There's a handful of other 
warnings when making, but --with-perl is the only showstopper 
(once the GNU_SOURCE problem is solved).

Peter chimed in:

> The underlying issue in clang has been resolved, so the next release
> should work out of the box.  I suggest we wait for that.
>
> http://llvm.org/bugs/show_bug.cgi?id=5365

Sweet, good to know. I'll update my clang repo and see if it does the 
trick.

- -- 
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 201011161302
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkzix3IACgkQvJuQZxSWSsgKxQCgl2vbUGS9plb1Zm7Sg+sdKR+5
oIUAn0CI9Dky2bQsYkoPhV6yZrQWosvQ
=f0+q
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: GiST insert algorithm rewrite
Next
From: Andy Colson
Date:
Subject: Re: unlogged tables