is this the issue that you faced with latest llvm?

[Maurizio Cimadamore]

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.