latest commit of panama-foreign branch jextract has strange error...

[mark.hammons at inaf.cnrs-gif.fr]

No, opensuse tumbleweed. I've tried a number of things, like "bash configure 
--disable-warnings-as-errors --with-jtreg=/home/mhammons/bin/jtreg --with-
libclang-include=/usr/include --with-libclang-include-aux=/usr/lib64 --enable-
headless-only" but jextract still fails to find stddef.h. Do I need to use a 
prebuilt clang that isn't from my linux distro?


On Friday, November 15, 2019 3:18:35 AM CET 
sundararajan.athijegannathan at oracle.com wrote:
> This does not appear to be due to last commit. Last commit was a hotspot
> fix to sync.  with latest hotspot code. That should not affect header
> file search. Are you on Mac?
> 
> -Sundar
> 
> On 15/11/19 5:51 am, Mark Hammons wrote:
> > I do not. This started happening with this build I'm trying to do of the
> > panama openjdk. I'm starting to think the stddef.h missing thing is on my
> > side, cause some of the jtreg tests failed with that too. Trying to figure
> > out why this is a problem for the build. Maybe it's because I'm using
> > clang 9.
> > 
> > ~Mark
> > 
> > On Friday, November 15, 2019 12:41:39 AM CET Maurizio Cimadamore wrote:
> >> Btw - are you saying you don't get this with the latest EA?
> >> 
> >> Maurizio
> >> 
> >> On 14/11/2019 23:38, Maurizio Cimadamore wrote:
> >>> Typically, the stddef.h not found problem comes from the fact that
> >>> jextract cannot find the clang support header files... is that a plain
> >>> call from command line? Which OS?
> >>> 
> >>> Thanks
> >>> Maurizio
> >>> 
> >>> On 14/11/2019 22:26, Mark Hammons wrote:
> >>>> Hi all,
> >>>> 
> >>>> When I use jextract from the latest panama-foreign commit
> >>>> (58596:ff086ae3cfac)
> >>>> I get the following error: java.lang.RuntimeException:
> >>>> /usr/include/zconf.h:
> >>>> 247:14: fatal error: 'stddef.h' file not found
> >>>> 
> >>>> it comes from this call of jextract: jextract /usr/include/zlib.h -L
> >>>> /usr/
> >>>> lib64 --record-library-path -l z -t zlib. I'm guessing this is a bug?
> >>>> 
> >>>> ~Mark