<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>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).</div><div><br></div><div>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.</div><div><br></div><div>++ kirk</div></div><div><br></div><div><div>On 2011-Jan-26, at 10:59 AM, ext Greg Clayton wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>This question would be better suited for the llvmdev list: <a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a><br><br>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).<br><br><br>On Jan 26, 2011, at 10:36 AM, <a href="mailto:kirk.beitz@nokia.com">kirk.beitz@nokia.com</a> wrote:<br><br><blockquote type="cite">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):<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">make[2]: Leaving directory `/x/lldb-win/tools/llvm-config'<br></blockquote><blockquote type="cite">llvm-config: unknown component name: bitreader<br></blockquote><blockquote type="cite">make[2]: Entering directory `/x/lldb-win/tools/opt'<br></blockquote><blockquote type="cite">/x/lldb-win/Makefile.rules:939: *** llvm-config --libs failed. Stop.<br></blockquote><blockquote type="cite">make[2]: Leaving directory `/x/lldb-win/tools/opt'<br></blockquote><blockquote type="cite">make[1]: *** [opt/.makeall] Error 2<br></blockquote><blockquote type="cite">make[1]: Leaving directory `/x/lldb-win/tools'<br></blockquote><blockquote type="cite">make: *** [all] Error 1<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">i browsed around in <a href="http://llvm.org/svn/llvm-project">http://llvm.org/svn/llvm-project</a> and don't see anything obvious called bitreader.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">i fgrep'ed for bitreader through what i did get co from svn, and i see some stuff under "bindings".<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">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.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">thanks for any info or help.<br></blockquote><blockquote type="cite">++ kirk<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 2011-Jan-25, at 4:43 PM, ext Greg Clayton wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">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.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">On linux, you checkout LLDB into the tools directory:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">svn co <a href="http://llvm.org/svn/llvm-project/llvm/trunk">http://llvm.org/svn/llvm-project/llvm/trunk</a> -r 123723 llvm<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">cd llvm/tools<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">svn co <a href="http://llvm.org/svn/llvm-project/cfe/trunk">http://llvm.org/svn/llvm-project/cfe/trunk</a> -r 123723 clang<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">svn co <a href="https://$USER@llvm.org/svn/llvm-project/lldb/trunk">https://$USER@llvm.org/svn/llvm-project/lldb/trunk</a> lldb<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">cd ..<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">./configure --enable-optimized --disable-assertions --enable-targets=x86_64,arm<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">make<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">This should just build everything you need.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">any information/help on any work already done on this front would be greatly appreciated.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Let me know if you have any other questions! But this should get you going.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Greg Clayton<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">++ kirk beitz : nokia : austin + san diego : <a href="mailto:kirk.beitz@nokia.com">kirk.beitz@nokia.com</a> ++<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">lldb-dev mailing list<br></blockquote><blockquote type="cite"><a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br></blockquote><blockquote type="cite"><a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev">http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev</a><br></blockquote><br></div></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="font-size: 11px; "><font class="Apple-style-span" face="Monaco"><span class="Apple-style-span" style="font-family: Helvetica; "><font class="Apple-style-span" face="Monaco"><br class="Apple-interchange-newline">++ kirk beitz : nokia : austin + san diego </font><span class="Apple-style-span" style="font-family: Monaco; ">: <a href="mailto:kirk.beitz@nokia.com">kirk.beitz@nokia.com</a> ++</span></span></font></div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></body></html>