| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: PG vs LLVM 12 on seawasp, next round |
| Date: | 2020-12-01 20:04:44 |
| Message-ID: | alpine.DEB.2.22.394.2012012058190.627870@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Thomas,
> Since seawasp's bleeding edge LLVM installation moved to "trunk
> 20201114 c8f4e06b 12.0.0" ~16 days ago, it has been red. Further
> updates didn't help it and it's now on "trunk 20201127 6ee22ca6
> 12.0.0". I wonder if there is something in Fabien's scripting that
> needs to be tweaked, perhaps a symlink name or similar.
The compiler compilation script is quite straightforward (basically, get
sources, configure and compile), even for a such a moving target…
The right approach is to wait for some time before looking at the issue,
typically one week for the next recompilation, in case the problem
evaporates, so you were right not to jump on it right away:-)
Andres investigated a few days ago, managed to reproduce the issue
locally, and has one line patch. I'm unsure if it should be prevently
back-patched, though.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-12-01 20:08:10 | Re: PG vs LLVM 12 on seawasp, next round |
| Previous Message | Chapman Flack | 2020-12-01 19:20:40 | Re: proposal: unescape_text function |