| From: | "Tom Turelinckx" <pgbf(at)twiska(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andres Freund" <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: snapper vs. HEAD |
| Date: | 2020-03-30 09:17:16 |
| Message-ID: | 0616f75a-d4a3-4276-8887-5462e530ce0a@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Tom Lane wrote:
> Confirmed: building gistget with --enable-cassert, and all of snapper's
> compile/link options, produces something that passes regression.
Skate uses buildfarm default configuration, whereas snapper uses settings which are used when building postgresql debian packages. Debian packages are built without --enable-cassert, but most buildfarm animals build with --enable-cassert. I specifically configured skate and snapper like that because I ran into such issues in the past (where debian packages would fail to build on sparc, but buildfarm animals on debian sparc did not highlight the issue).
In the past, I've already switched from gcc 4.6 to gcc 4.7 as a workaround for a similar compiler bug, but I can't upgrade to a newer gcc without backporting it myself, so for the moment I've switched snapper to use -O1 instead of -O2, for HEAD only.
Not sure whether wheezy on sparc 32-bit is very relevant today, but it's an exotic platform, so I try to keep those buildfarm animals alive as long as it's possible.
Best regards,
Tom Turelinckx
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2020-03-30 09:49:00 | Re: Berserk Autovacuum (let's save next Mandrill) |
| Previous Message | Magnus Hagander | 2020-03-30 09:06:45 | Re: Possible copy and past error? (\usr\backend\commands\analyze.c) |