The old drlvm build is no longer supported, did you try the new one?
--
Alexey

2008/2/8, Aleksey Shipilev <[EMAIL PROTECTED]>:
> Hi,
>
> I had updated to fresh revision and see the build on Windows/ia32 is broken.
> Errors lead to verifier, so I had tested this commit:
>
> 619918 - build FAILED with [1]
> 619847 - build FAILED with [1]
> 619846 - build OK
> 618000 - build OK
>
> Mikhail, can you look what's happening?
>
> Thanks,
> Aleksey.
>
> [1] tail of build log
> build.native.cpp:
>       [cc] Starting dependency analysis for 193 files.
>       [cc] 193 files are up to date.
>       [cc] 0 files to be recompiled from dependency analysis.
>       [cc] 0 total files to be compiled.
>
> build.native.asm.init:
>
> build.native.asm:
>
> build.native.link.init:
>
> build.native.link:
>       [cc] 0 total files to be compiled.
>       [cc] Starting link
>       [cc]    Creating library harmonyvm.lib and object harmonyvm.exp
>       [cc] recompute.obj : error LNK2019: unresolved external symbol
> "void __cdecl method_modify_exc_handler_info(struc
> t Method_ *,unsigned short,unsigned short,unsigned short,unsigned
> short,unsigned short)" (?method_modify_exc_handler_inf
> o@@YAXPAUMethod_@@[EMAIL PROTECTED]) referenced in function "protected: void
> __thiscall CPVerifier_5::vf_Context_5e::reduceTryBloc
> ks(unsigned short,unsigned short)"
> ([EMAIL PROTECTED]@CPVerifier_5@@[EMAIL PROTECTED])
>       [cc] recompute.obj : error LNK2019: unresolved external symbol
> "void __cdecl method_remove_exc_handler(struct Met
> hod_ *,unsigned short)"
> (?method_remove_exc_handler@@YAXPAUMethod_@@[EMAIL PROTECTED]) referenced in
> function "protected: void __thisc
> all CPVerifier_5::vf_Context_5e::reduceTryBlocks(unsigned
> short,unsigned short)" ([EMAIL PROTECTED]@CPVerif
> ier_5@@[EMAIL PROTECTED])
>       [cc] write_attr.obj : error LNK2019: unresolved external symbol
> "unsigned short __cdecl class_get_cp_class_entry(
> struct Class_ *,char const *)"
> (?class_get_cp_class_entry@@YAGPAUClass_@@[EMAIL PROTECTED]) referenced in
> function "protected: void
> __thiscall CPVerifier_5::vf_Context_5e::writeStackMapElements(unsigned
> int,unsigned int)" ([EMAIL PROTECTED]
> [EMAIL PROTECTED]@@[EMAIL PROTECTED])
>       [cc] harmonyvm.dll : fatal error LNK1120: 3 unresolved externals
>
> BUILD FAILED
> C:\Harmony\trunk\working_vm\build\make\build.xml:600: The following
> error occurred while executing this line:
> C:\Harmony\trunk\working_vm\build\make\build.xml:607: The following
> error occurred while executing this line:
> C:\Harmony\trunk\working_vm\build\make\build_component.xml:74: The
> following error occurred while executing this line:
> C:\Harmony\trunk\working_vm\build\make\targets\build.native.xml:222:
> link failed with return code 1120
>
> Total time: 1 minute 13 seconds
>
>
> ---------- Forwarded message ----------
> From:  <[EMAIL PROTECTED]>
> Date: Feb 8, 2008 2:53 PM
> Subject: svn commit: r619847 - in /harmony/enhanced/drlvm/trunk:
> make/vm/ vm/vmcore/src/verifier-3363/x_verifier/
> To: [EMAIL PROTECTED]
>
>
> Author: mloenko
> Date: Fri Feb  8 03:53:11 2008
> New Revision: 619847
>
> URL: http://svn.apache.org/viewvc?rev=619847&view=rev
> Log:
> intergration of HARMONY-5142 (implementation of recompute stackmap) -
> patch was modified a bit
>
> Added:
>    harmony/enhanced/drlvm/trunk/vm/vmcore/src/verifier-3363/x_verifier/
>    
> harmony/enhanced/drlvm/trunk/vm/vmcore/src/verifier-3363/x_verifier/recompute.cpp
>  (with props)
>    
> harmony/enhanced/drlvm/trunk/vm/vmcore/src/verifier-3363/x_verifier/recompute.h
>  (with props)
>    
> harmony/enhanced/drlvm/trunk/vm/vmcore/src/verifier-3363/x_verifier/write_attr.cpp
>  (with props)
>    
> harmony/enhanced/drlvm/trunk/vm/vmcore/src/verifier-3363/x_verifier/x_class_interface.h
>  (with props)
>    
> harmony/enhanced/drlvm/trunk/vm/vmcore/src/verifier-3363/x_verifier/x_verifier.cpp
>  (with props)
>    
> harmony/enhanced/drlvm/trunk/vm/vmcore/src/verifier-3363/x_verifier/x_verifier.h
>  (with props)
> Modified:
>    harmony/enhanced/drlvm/trunk/make/vm/verifier.xml
>

Reply via email to