harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Volosyuk (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-443) Compilation fixes for DRLVM on gcc-3.4.6
Date Fri, 05 May 2006 14:42:27 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-443?page=all ]

Ivan Volosyuk updated HARMONY-443:

    Attachment: DRLVM-GCC-3.4_and_4.x-cumulative.patch

Here is cumulative patch which fixes compilation problems on GCC-3.4.x and GCC-4.x compilers.
DRLVM works fine (eclipse starts) compiled by any versions of GCC now.
It also still compiles and works on windows built with icl or msvc.net.

The patch makes obsolete all previous patches here, so remove them before applying this patch.

   Copy it to Harmony directory.
   Run: patch -p1 < DRLVM-GCC-3.4_and_4.x-cumulative.patch
   Change directory to build
      build update

It is _impotant_ to run 'build update' for changes in log4cxx to take place.

Tested on:
    Gentoo / GCC-3.4.6
    Gentoo / GCC-4.1.0
    Suse / GCC-3.3.3
    WinXp / icl 9.0 p25
    WinXp / cl 13.10.3077


> Compilation fixes for DRLVM on gcc-3.4.6
> ----------------------------------------
>          Key: HARMONY-443
>          URL: http://issues.apache.org/jira/browse/HARMONY-443
>      Project: Harmony
>         Type: Improvement

>   Components: VM
>  Environment: Debian linux, gcc-3.4.6
>     Reporter: Ivan Volosyuk
>  Attachments: DRLVM-GCC-3.4_and_4.x-cumulative.patch, DRLVM-gcc-3.4.6.diff, DRLVM-gcc-4.1.0.diff,
DRLVM-log4cxx-gcc-4.1.0.diff, DRLVM-log4cxx-gcc-4_1_0-patch.zip
> I have made a patch which fixes DRLVM compilation problem with gcc-3.4.6.
> The project still compiles fine with gcc-3.3.6.
> Fixed jitrino/**/Stl.h to have correct begin(), end() statements
> Some fixes in jitrino
> Fixed problem with missing header: ext/stl_map_func.h:
> Header "ext/map_func.h" is used for GCC > 3.4 otherwise "ext/stl_map_func.h" is used.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message