| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: GCC vs clang |
| Date: | 2010-11-16 18:10:15 |
| Message-ID: | 2258.1289931015@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
> 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).
I'm hesitant to put in a patch that breaks plperl, even if it's for
a situation where you otherwise couldn't build at all; because plperl
would still be broken after the clang problem is resolved.
Better to get a fixed copy of clang.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-16 18:12:20 | Re: unlogged tables |
| Previous Message | Andy Colson | 2010-11-16 18:09:47 | Re: unlogged tables |