Re: PG vs LLVM 12 on seawasp, next round - Mailing list pgsql-hackers

From Andres Freund
Subject Re: PG vs LLVM 12 on seawasp, next round
Date
Msg-id 20201201064949.mex6kvi2kygby3ni@alap3.anarazel.de
Whole thread Raw
In response to PG vs LLVM 12 on seawasp, next round  (Thomas Munro <thomas.munro@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: TAP test utility module 'PG_LSN.pm'
Next
From: Masahiko Sawada
Date:
Subject: Re: autovac issue with large number of tables