| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c |
| Date: | 2010-04-02 05:05:11 |
| Message-ID: | 4BB57B07.4030900@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/1/10 9:57 PM, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Hmmm. I appear to have had a compile error with that alpha5 tarball,
>> in elog.c. No special options on compile, except an alternate directory
>> and port.
>
> No, you stuck in -Werror. Don't do that on bleeding-edge gcc (or
> bleeding-edge anything).
I didn't actually. Must be set by default on Ubuntu's gcc?
(goes looking for a way to disable it ...)
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-04-02 05:10:25 | Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c |
| Previous Message | Tom Lane | 2010-04-02 04:57:45 | Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c |