is this the issue that you faced with latest llvm?

[Jorn Vernee]

Note that there are several extra configure options to specify the LLVM 
directories:

   --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 we don't have an option to select an LLVM version (yet?), 
explicitly setting some of these might have the same effect.

Jorn

Maurizio Cimadamore schreef op 2019-05-03 13:27:
> You mean fail configure step if wrong version is used? If so, that
> would be desirable, yes
> 
> Maurizio
> 
> On 03/05/2019 11:18, James Laskey wrote:
>> Could we have an option to point to a specific version of LLVM?
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2019, at 7:03 AM, Maurizio Cimadamore 
>>> <maurizio.cimadamore at oracle.com> wrote:
>>> 
>>> I get the same with LLVM 8 on Ubuntu 16.04 -- e.g. missing structs 
>>> leading to errors like:
>>> 
>>> /usr/include/_G_config_h.java:87: error: cannot find symbol
>>>         public void __state$set(usr.include.wchar_h.__mbstate_t 
>>> value);
>>> 
>>> 
>>> 
>>> 
>>> I think at this point in time it's safe to assume that the latest 
>>> LLVM supported by Panama is LLVM 7.
>>> 
>>> Maurizio
>>> 
>>>> On 02/05/2019 14:06, Jorn Vernee wrote:
>>>> Hi Sundar,
>>>> 
>>>> No, this looks like another issue. The issue I found did not cause a 
>>>> StackOverflowError. It only caused struct/union classes to not be 
>>>> generated.
>>>> 
>>>> Cheers,
>>>> Jorn
>>>> 
>>>> Sundararajan Athijegannathan schreef op 2019-05-02 14:59:
>>>>> Hi Jorn,
>>>>> 
>>>>> Jim Laskey is facing this issue ->
>>>>> https://bugs.openjdk.java.net/browse/JDK-8223238
>>>>> 
>>>>> Is this the same jextract issue you faced with the latest llvm? or
>>>>> something else?
>>>>> 
>>>>> Thanks
>>>>> -Sundar