On 21/03/2019 15:49, Erik Joelsson wrote:
> I don't think anyone has tried. Just removing the check in configure
> should be simple enough, but I suspect there will be lots of follow-on
> issues.
>
> /Erik
>
> On 2019-03-21 03:05, Langer, Christoph wrote:
>> Hi,
>>
>> the Mac experts will
Hi Erik,
在 2019年03月20日 00:51, Erik Joelsson 写道:
Hello Leslie,
The failure you see is happening when the newly built exploded image
is used for the first time. I'm not familiar with ASAN, but it seems
that the JDK you create does not quite work. There are some ways
around this.
Indeed.
This patch adds a missing RPATH to libjvm.so which is needed when
bundling libffi.so for zero builds. The rpath is only added when
building zero and bundling of libffi is enabled. When linking with bfd
(the old binutils linker), it seems that the rpath of the library that
loaded libjvm.so
I don't think anyone has tried. Just removing the check in configure
should be simple enough, but I suspect there will be lots of follow-on
issues.
/Erik
On 2019-03-21 03:05, Langer, Christoph wrote:
Hi,
the Mac experts will probably find my question to be silly and start laughing…
but
On 3/20/19 3:53 PM, Andrew John Hughes wrote:
> On 19/03/2019 15:09, Martin Buchholz wrote:
>> Probably it's because glibc deprecated readdir, and we don't have
>> --disable-warnings-as-errors by default?
>>
>> (I think warnings should not be errors except as opt-in by openjdk
>>
Hi,
the Mac experts will probably find my question to be silly and start laughing…
but nevertheless, I’m asking it here
I was looking into building OpenJDK 8 today on my developer Mac, which runs
Mojave (10.14.3). configure immediately tells me, I need Xcode 4. So I was
trying to install
