harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Salikh Zakirov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-898) workaround to get correct hythr.dll
Date Mon, 17 Jul 2006 12:43:14 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-898?page=all ]

Salikh Zakirov updated HARMONY-898:

    Attachment: 0001-Workaround-to-avoid-copying-hythr-from-classlib-s-bin-directory.patch

The attached trivial patch makes the build system predictable:
it never tries to copy Classlib's hythr to jre/bin.

While the issue is more serious, and should be resolved differently
by removing duplicated hythr libraries.
I suggest to apply this patch before the issue is resolved properly,
to make the DRLVM build more stable.

> workaround to get correct hythr.dll
> -----------------------------------
>                 Key: HARMONY-898
>                 URL: http://issues.apache.org/jira/browse/HARMONY-898
>             Project: Harmony
>          Issue Type: Bug
>         Environment: Windows, Linux
>            Reporter: Salikh Zakirov
>         Attachments: 0001-Workaround-to-avoid-copying-hythr-from-classlib-s-bin-directory.patch
> Currently, DRLVM builds a replacement hythr library, implementing the same interface.
> The build system currently does not guarantee which version will end up in deploy/jre/bin,
> and, at random, either of the version could get to jre/bin.
> My informal observations are
> * a fresh build puts DRLVM's hythr to jre/bin, and the system works
> * an incremental rebuild puts Classlib's hythr to jre/bin, and the system crashes with
>    after reading NULL from TLS.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message