is this the issue that you faced with latest llvm?

[Jim Laskey]

Actually more general. We have several problems currently all based on the fact we make way too many assumptions about the llvm configuration.

0. --with-libclang=/usr/local is too generalized. You should be able to --with-libclang=/usr/local/lib/clang/9.0.0/.
1. llvm is not always in a fixed location, whether it be per platform or whether it be a local build.
2. The current look up of llvm is very fragile, taking the highest platform ordered entry in the release directory.  Eg. will find 9.0.0 but will mess up when 10.0.0 is installed.
3. Wrongly assumes naiveté on the users part. Maybe jextract doesn't work on 8 and 9 but if the user wants to try fixes in 9 or 10, they should be allowed to do so.
4. The shipping jdk jextract configuration may be different that what the user has installed.

Allowing the specification of llvm locale on jextract itself would resolve these issues.

-- Jim


> On May 3, 2019, at 8:27 AM, Maurizio Cimadamore <maurizio.cimadamore at oracle.com> wrote:
> 
> 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