is this the issue that you faced with latest llvm?

Maurizio Cimadamore maurizio.cimadamore at oracle.com
Fri May 3 13:27:46 UTC 2019


I'll try this with our internal build infra used for EA first... :-)

Maurizio


On 03/05/2019 14:25, Jorn Vernee wrote:
> I've made a quick patch that does some basic version checking and also 
> allows selection of a specific LLVM version: 
> http://cr.openjdk.java.net/~jvernee/panama/webrevs/llvmconf/webrev.00/
>
> This picks a version matching '7' by default, and allows specifying 
> another version using e.g. --with-libclang-version=8, but also 
> supports more complex version strings like 8.0.1 (using grep). If the 
> selected version can not be found a config error is emitted. The 
> version is ignored if --with-libclang-include-aux is specified 
> manually (which is AFAIK the only place where the version matters).
>
> Jorn
>
> Maurizio Cimadamore schreef op 2019-05-03 14:30:
>> The current system is mostly design to work with prebuilt binaries here:
>>
>> http://releases.llvm.org/download.html
>>
>> You can point the Panama JDK to any binary snapshot you want in there
>> and it just works (I tried earlier with several version to see if I
>> was able to reproduce some issues).
>>
>> If you want the Panama build to work with system installation of
>> clang/LLVM, you need to use separate configure options to tell the
>> build where to find
>>
>> 1) the libclang includes
>> 2) the libclang.so lib
>> 3) the aux include files shipped with LLVM
>>
>> $ sh configure --help | grep clang   --with-libclang=<path to llvm>
>>                           Specify path of llvm installation containing
>>                           libclang. Pre-built llvm binary can be 
>> downloaded
>>                           from http://llvm.org/releases/download.html
>>   --with-libclang-lib=<path>
>>                           Specify where to find libclang binary, 
>> so/dylib/lib
>>   --with-libclang-include=<path>
>>                           Specify where to find libclang header files,
>>                           clang-c/Index.h
>>   --with-libclang-include-aux=<path>
>>                           Specify where to find libclang auxiliary 
>> header
>>                           files, 
>> lib/clang/<clang-version>/include/stddef.h
>>   --with-libclang-bin=<path>
>>                           Specify where to find clang binary, 
>> libclang.dll
>>
>> While this can be improved, it seems somewhat documented, and has
>> worked for us so far.
>>
>> Doing --with-libclang=/usr/local/lib/clang/9.0.0/ doesn#'t really make
>> sense in the current system.
>>
>> Maurizio
>>
>> On 03/05/2019 12:57, Jim Laskey wrote:
>>> Allowing the specification of llvm locale on jextract itself would 
>>> resolve these issues.


More information about the panama-dev mailing list