building loom

[Peter Fraenkel]

Linux RH 7, but I think the issue is that valgrind was available, causing CALLGRIND_START_INSTRUMENTATION to be set, exposing a block in continuation.cpp that referred to _cgrind_interpreted_frames, which doesn’t seem to be defined anywhere.  If I edit the source and #undef it explicitly, the build completes.   Now I can live my hsdis dreams.

> On Dec 29, 2020, at 3:45 PM, David Holmes <david.holmes at oracle.com> wrote:
> 
> Hi Peter,
> 
> On 30/12/2020 3:13 am, Peter Fraenkel wrote:
>> Hi -
>> The loom early access loom builds are “based on” jdk-16+25, but
>> obviously not identical.  While I can build jdk-16+25 (and every other
>> tag I’ve tried) from  github openjdk/jdk, the current HEAD of the fibers
>> branch of openjdk/loom (711119b) has compilation errors.  Before
>> investigating them too deeply, I want to make sure I’m actually building
>> something that is expected to compile.  
> 
> Our Loom CI builds are fine, what platform are you seeing a problem on?
> 
> Cheers,
> David
> 
>> The openjdk/loom repo only has
>> tags up to jdk-15+1.  Is there a way to find the commit corresponding to
>> a particular early access build?
>> - Peter
> 
> 
>