harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5032) [drlvm][port] drlvm is not buildable on linux em64t
Date Tue, 30 Oct 2007 14:38:53 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538789
] 

Alexey Varlamov commented on HARMONY-5032:
------------------------------------------

Ah, these details clarify the issue. Which JRE do you use for building - 32 bit or 64 bit?
Looks like the first one; then you actually worked with the mixed build, i.e. classlib natives
were 32-bit libs. I recall this have been discussed on list and recorded somewhere on wiki
as a rule of thumb: it is preferable to use native JRE for the target platform.

The change you refer to is towards properties unification between classlib and drlvm. It is
not complete though, otherwise you'd get pure 32-build instead :)

> [drlvm][port] drlvm is not buildable on linux em64t
> ---------------------------------------------------
>
>                 Key: HARMONY-5032
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5032
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: linux em64t
>            Reporter: Sergey Dmitriev
>            Priority: Critical
>
> Just have discovered that today-yesterday's DRLVM (r588319) is not buildable on Linux
em64t.
> Note that 22 october version is ok.
> {guy@earth:~/harmony.26oct/working_vm/build} ./build.sh -DBUILD_CFG=release
> . . .
> build:
> build_vm.port:
> pre_init:
> common_vm:
> Overriding previous definition of reference to common.compiler
> Overriding previous definition of reference to common.cpp.compiler
> Overriding previous definition of reference to common.c.compiler
> Overriding previous definition of reference to common.linker
> init:
> Overriding previous definition of reference to asm.fileset
> init_component:
> build.java:
> build.jar:
> build.native.init:
>      [echo] ## Building native of 'vm.port'
>     [mkdir] Created dir: /export/harmony.26oct/working_vm/build/lnx_em64t_gcc_release/semis/vm/port
>     [mkdir] Created dir: /export/harmony.26oct/working_vm/build/lnx_em64t_gcc_release/semis/vm/port/_bin
>     [mkdir] Created dir: /export/harmony.26oct/working_vm/build/lnx_em64t_gcc_release/semis/vm/port/_obj
> build.native.c:
>        [cc] 11 total files to be compiled.
>        [cc] /export/harmony.26oct/working_vm/vm/port/src/disasm/linux/disasm.c: In function
`disasm_print':
>        [cc] /export/harmony.26oct/working_vm/vm/port/src/disasm/linux/disasm.c:125: warning:
cast from pointer to integer of different size
>        [cc] /tmp/ccL6oUxH.s: Assembler messages:
>        [cc] /tmp/ccL6oUxH.s:134: Error: `0(%esp)' is not a valid 64 bit base/index expression
> BUILD FAILED
> /export/harmony.26oct/working_vm/build/make/build.xml:543: The following error occurred
while executing this line:
> /export/harmony.26oct/working_vm/build/make/build.xml:550: The following error occurred
while executing this line:
> /export/harmony.26oct/working_vm/build/make/build_component.xml:73: The following error
occurred while executing this line:
> /export/harmony.26oct/working_vm/build/make/targets/build.native.xml:91: gcc failed with
return code 1
> Total time: 1 minute 54 seconds
> *
> * Please, refer to README.txt for details.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message