after digging into this further in my build logs, i saw that i did not clean up properly after a previous interim failure (due to an environment variable name collision that i resolved and attempted to re-configure, but did not properly clean up).
after a full 'make clean', the libclang .a files all appear to have been built as necessary, and i'm moving on to getting lldb to build. ++ kirk On 2011-Jan-26, at 10:59 AM, ext Greg Clayton wrote: This question would be better suited for the llvmdev list: [email protected]<mailto:[email protected]> I am not sure what bitreader is used for, but if I had to guess, I would guess it is needed (possibly by the assembler, disassembler, codegen etc). On Jan 26, 2011, at 10:36 AM, [email protected]<mailto:[email protected]> wrote: a bit more info … i want to get lldb built using mingw. llvm's configure seems to create Makefiles in most appropriate places. i've got as far as the following (with a workaround for a PERL variable dependency that chokes if the containing windows environment contains a PERL variable that has a windows-specific full-path name): make[2]: Leaving directory `/x/lldb-win/tools/llvm-config' llvm-config: unknown component name: bitreader make[2]: Entering directory `/x/lldb-win/tools/opt' /x/lldb-win/Makefile.rules:939: *** llvm-config --libs failed. Stop. make[2]: Leaving directory `/x/lldb-win/tools/opt' make[1]: *** [opt/.makeall] Error 2 make[1]: Leaving directory `/x/lldb-win/tools' make: *** [all] Error 1 i browsed around in http://llvm.org/svn/llvm-project and don't see anything obvious called bitreader. i fgrep'ed for bitreader through what i did get co from svn, and i see some stuff under "bindings". do i really need 'bitreader' for lldb? is there already a way to turn off support for trying to make it using configure? if it's not needed for lldb, and if configure doesn't already have a way to ignore it, i'll see if i can tweak configure to do so. thanks for any info or help. ++ kirk On 2011-Jan-25, at 4:43 PM, ext Greg Clayton wrote: i had been of the understanding that some work is being done on building lldb for linux … which would imply that something similar has to be done with linux-specific archives and tools … given that the committed llvm.zip contains mac "fat" archives, and that the extraction scripts use the mac/darwin tool 'lipo' to extract the archives for use in building lldb. On linux, you checkout LLDB into the tools directory: svn co http://llvm.org/svn/llvm-project/llvm/trunk -r 123723 llvm cd llvm/tools svn co http://llvm.org/svn/llvm-project/cfe/trunk -r 123723 clang svn co https://[email protected]/svn/llvm-project/lldb/trunk lldb cd .. ./configure --enable-optimized --disable-assertions --enable-targets=x86_64,arm make This should just build everything you need. any information/help on any work already done on this front would be greatly appreciated. Let me know if you have any other questions! But this should get you going. Greg Clayton ++ kirk beitz : nokia : austin + san diego : [email protected]<mailto:[email protected]> ++ _______________________________________________ lldb-dev mailing list [email protected]<mailto:[email protected]> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev ++ kirk beitz : nokia : austin + san diego : [email protected]<mailto:[email protected]> ++
_______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
