Re: PG vs LLVM 12 on seawasp, next round
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-02-15T19:41:39Z
Lists: pgsql-hackers
>> I've added an explicit LD_LIBRARY_PATH, which will be triggered at some >> point later. This seems to have fixed the issue. I'm sorry for the noise and quite baffled anyway, because according to my change logs it does not seem that I modified anything from my side about the dynamic library path when compiling with clang. At least I do not see a trace of that. > You can also do something like LDFLAGS="$LDFLAGS -Wl,-rpath,$(llvm-config --libdir)" > or such. I've resorted to just hardcode LD_LIBRARY_PATH alongside PATH when compiling with clang in my buildfarm script. Thanks for the tip anyway. And thanks Thomas for pointing out the fix! -- Fabien.
Commits
-
jit: configure: Explicitly reference 'native' component.
- 9543f0861b1d 14.0 landed
- f4f924b3ed77 11.11 landed
- b07490b91246 12.6 landed
- 4f64daf73af7 13.2 landed