From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Subject: | Re: PG vs LLVM 12 on seawasp, next round |
Date: | 2020-12-01 06:49:49 |
Message-ID: | 20201201064949.mex6kvi2kygby3ni@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2020-12-01 17:35:49 +1300, Thomas Munro wrote:
> 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. I don't
> follow LLVM development but I found my way to a commit[1] around the
> right time that mentions breaking up the OrcJIT library, so *shrug*
> maybe that's a clue.
>
> +ERROR: could not load library
> "/home/fabien/pg/build-farm-11/buildroot/HEAD/pgsql.build/tmp_install/home/fabien/pg/build-farm-11/buildroot/HEAD/inst/lib/postgresql/llvmjit.so":
> libLLVMOrcJIT.so.12git: cannot open shared object file: No such file
> or directory
It's a change in how LLVM dependencies are declared
internally. Previously the 'native' component was - unintentionally -
transitively included via the 'orcjit' component, but now that's not the
case anymore.
The attached patch should fix it, I think?
Greetings,
Andres Freund
Attachment | Content-Type | Size |
---|---|---|
llvm-build.diff | text/x-diff | 1.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2020-12-01 07:23:36 | Re: autovac issue with large number of tables |
Previous Message | Michael Paquier | 2020-12-01 06:27:01 | Re: TAP test utility module 'PG_LSN.pm' |