[LLVMdev] [vmkit] Errors compiling vmkt

[Harris Bakiras]

Hi Chris,

For the moment you can install VMKit following these instructions:

     http://vmkit2.gforge.inria.fr/start.php

VMKit's web page and repository will be updated soon.

Harris Bakiras

Le 12/02/2013 10:30, chris.gray at kiffer.be a écrit :
> Hi all,
>
> I hope this is the correct place to post such questions?  I am building
> vmkit for the first time, following the instructions on the get_started
> page (with one deviation: in step 4 I ran ./configure in my vmkit
> directory and therefore did not need to cd at the start of step 5.  Is
> this correct?). Build platform is 64-bit CrunchBang Linux 11 "Waldorf",
> based on Debian Wheezy.
>
> I get some compilation warnings, which could be harmless, followed by an
> error:
>
> chris at forbesy:~/vmkit$ make ENABLE_OPTIMIZED=1llvm[0]: Constructing
> LLVMBuild project information.
> make[1]: Entering directory `/home/chris/vmkit/lib/vmkit/StaticGCPass'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/home/chris/vmkit/lib/vmkit/StaticGCPass'
> make[1]: Entering directory `/home/chris/vmkit/lib/vmkit/StaticGCPrinter'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/home/chris/vmkit/lib/vmkit/StaticGCPrinter'
> make[1]: Entering directory `/home/chris/vmkit/lib'
> make[2]: Entering directory `/home/chris/vmkit/lib/vmkit'
> make[3]: Entering directory `/home/chris/vmkit/lib/vmkit/CommonThread'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/chris/vmkit/lib/vmkit/CommonThread'
> make[3]: Entering directory `/home/chris/vmkit/lib/vmkit/MMTk'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/chris/vmkit/lib/vmkit/MMTk'
> make[3]: Entering directory `/home/chris/vmkit/lib/vmkit/Runtime'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/chris/vmkit/lib/vmkit/Runtime'
> make[3]: Entering directory `/home/chris/vmkit/lib/vmkit/Compiler'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/chris/vmkit/lib/vmkit/Compiler'
> make[3]: Entering directory `/home/chris/vmkit/lib/vmkit/JITGCPass'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/chris/vmkit/lib/vmkit/JITGCPass'
> make[2]: Leaving directory `/home/chris/vmkit/lib/vmkit'
> make[2]: Entering directory `/home/chris/vmkit/lib/j3'
> make[3]: Entering directory `/home/chris/vmkit/lib/j3/LLVMRuntime'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/chris/vmkit/lib/j3/LLVMRuntime'
> make[3]: Entering directory `/home/chris/vmkit/lib/j3/VMCore'
> llvm[3]: Compiling JnjvmClassLoader.cpp for Release+Asserts build (bytecode)
> warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
>        '-Wno-uninitialized'? [-Wunknown-warning-option]
> In file included from JnjvmClassLoader.cpp:30:
> /home/chris/vmkit/lib/j3/VMCore/../ClassLib/GNUClasspath/ClasspathReflect.h:153:8:
> warning:
>        private field 'running' is not used [-Wunused-private-field]
>    bool running;
>         ^
> /home/chris/vmkit/lib/j3/VMCore/../ClassLib/GNUClasspath/ClasspathReflect.h:206:15:
> warning:
>        private field 'nextOnQueue' is not used [-Wunused-private-field]
>    JavaObject* nextOnQueue;
>                ^
> 3 warnings generated.
> llvm[3]: Compiling JnjvmClassLoader.ll to JnjvmClassLoader.bc for
> Release+Asserts build (bytecode)
> llvm[3]: Compiling JnjvmClassLoader.bc to JnjvmClassLoader.s for
> Release+Asserts build
> llvm[3]: Compiling JnjvmClassLoader.s for Release+Asserts build
> llvm[3]: Building Release+Asserts Archive Library libJ3.a
> make[3]: Leaving directory `/home/chris/vmkit/lib/j3/VMCore'
> make[3]: Entering directory `/home/chris/vmkit/lib/j3/ClassLib'
> make[4]: Entering directory `/home/chris/vmkit/lib/j3/ClassLib/GNUClasspath'
> llvm[4]: Compiling JavaUpcalls.cpp for Release+Asserts build (bytecode)
> warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
>        '-Wno-uninitialized'? [-Wunknown-warning-option]
> In file included from JavaUpcalls.cpp:10:
> /home/chris/vmkit/lib/j3/ClassLib/GNUClasspath/ClasspathReflect.h:153:8:
> warning:
>        private field 'running' is not used [-Wunused-private-field]
>    bool running;
>         ^
> /home/chris/vmkit/lib/j3/ClassLib/GNUClasspath/ClasspathReflect.h:206:15:
> warning:
>        private field 'nextOnQueue' is not used [-Wunused-private-field]
>    JavaObject* nextOnQueue;
>                ^
> 3 warnings generated.
> llvm[4]: Compiling JavaUpcalls.ll to JavaUpcalls.bc for Release+Asserts
> build (bytecode)
> llvm[4]: Compiling JavaUpcalls.bc to JavaUpcalls.s for Release+Asserts build
> llvm[4]: Compiling JavaUpcalls.s for Release+Asserts build
> llvm[4]: Building Release+Asserts Archive Library libClasspath.a
> make[4]: Leaving directory `/home/chris/vmkit/lib/j3/ClassLib/GNUClasspath'
> make[3]: Leaving directory `/home/chris/vmkit/lib/j3/ClassLib'
> make[3]: Entering directory `/home/chris/vmkit/lib/j3/Compiler'
> llvm[3]: Compiling JavaJIT.cpp for Release+Asserts build (bytecode)
> warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
>        '-Wno-uninitialized'? [-Wunknown-warning-option]
> JavaJIT.cpp:1262:23: error: no member named 'removeFnAttr' in
> 'llvm::Function'
>          llvmFunction->removeFnAttr(
>          ~~~~~~~~~~~~  ^
> 1 warning and 1 error generated.
> make[3]: ***
> [/home/chris/vmkit/lib/j3/Compiler/Release+Asserts/JavaJIT.ll] Error 1
> make[3]: Leaving directory `/home/chris/vmkit/lib/j3/Compiler'
> make[2]: *** [all] Error 1
> make[2]: Leaving directory `/home/chris/vmkit/lib/j3'
> make[1]: *** [j3/.makeall] Error 2
> make[1]: Leaving directory `/home/chris/vmkit/lib'
> make: *** [all] Error 1
>
> Did I do something wrong?
>
> Regards
>
> Chris
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev