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

From Fabien COELHO
Subject Re: PG vs LLVM 12 on seawasp, next round
Date
Msg-id alpine.DEB.2.22.394.2102152036460.1209601@pseudo
Whole thread Raw
In response to Re: PG vs LLVM 12 on seawasp, next round  (Andres Freund <andres@anarazel.de>)
List 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.



pgsql-hackers by date:

Previous
From: Mark Rofail
Date:
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Next
From: Andrew Dunstan
Date:
Subject: Re: PG vs LLVM 12 on seawasp, next round