Staffan,
For instance, CLHSDB not able to initialize js engine.
Exception in thread "main" java.lang.RuntimeException: can't load
JavaScript engine
at
sun.jvm.hotspot.utilities.soql.JSJavaScriptEngine.<init>(JSJavaScriptEngine.java:447)
at
sun.jvm.hotspot.utilities.soql.JSJavaScriptEngine.<init>(JSJavaScriptEngine.java:464)
at
sun.jvm.hotspot.CommandProcessor$51.<init>(CommandProcessor.java:1709)
at
sun.jvm.hotspot.CommandProcessor.postAttach(CommandProcessor.java:1709)
at
sun.jvm.hotspot.CommandProcessor.<init>(CommandProcessor.java:1780)
at sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:98)
at sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:40)
-Dmitry
On 2013-09-16 13:46, Staffan Larsen wrote:
> What more than sa-jdi.jar and libsaproc do you need? Both of those are built
> with "normal" hotspot or jdk builds.
>
> /Staffan
>
> On 16 sep 2013, at 11:06, Dmitry Samersoff <dmitry.samers...@oracle.com>
> wrote:
>
>> Hi Everyone,
>>
>> How I can have hsdb built with new build system?
>>
>> Currently I'm building sa-jdi part of hsdb together with res of JDK,
>> than I have to go hotspot/agent/make, set all ALT_* variables and type
>> make here.
>>
>> Is there a better way?
>>
>> -Dmitry
>>
>> --
>> Dmitry Samersoff
>> Oracle Java development team, Saint Petersburg, Russia
>> * I would love to change the world, but they won't give me the sources.
>
--
Dmitry Samersoff
Oracle Java development team, Saint Petersburg, Russia
* I would love to change the world, but they won't give me the sources.
