| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG vs LLVM 12 on seawasp, next round |
| Date: | 2021-02-15 19:41:39 |
| Message-ID: | alpine.DEB.2.22.394.2102152036460.1209601@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-02-15 19:50:34 | Re: PG vs LLVM 12 on seawasp, next round |
| Previous Message | Mark Rofail | 2021-02-15 19:34:54 | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |