<div dir="ltr"><div class="gmail_quote">On Mon, Mar 30, 2015 at 5:58 PM David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Mar 30, 2015 at 2:47 PM, Chandler Carruth <span dir="ltr"><<a href="mailto:chandlerc@gmail.com" target="_blank">chandlerc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Looks like the binaries weren't built against tinfo correctly.<br></div></blockquote></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br>Should they be?</div></div></div></div></blockquote><div><br></div><div>If the OS they're targeting uses libtinfo, yes. If it just uses libncurses, it should link against that.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> Does that make a hard dependence on that?</div></div></div></div></blockquote><div><br></div><div>There are lots of distros and OSes which don't need or want it? There are also users that don't want it?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Is that what we want for the published binaries & we just tell users it's a hard dependency they have to install?<br></div></div></div></div></blockquote><div><br></div><div>I think for packages being installed onto OSes which by default have these, the packages should by default use them. We're talking about ncurses and tinfo, and so I think it's a pretty mundane install requirement for debian or ubuntu systems. Similarly for fedora or redhat.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br>(Perhaps it's a trivial "yes" to all this - I just have no clue here)<br> </div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"></div><div><div><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 2:30 PM David Blaikie <<a href="mailto:dblaikie@gmail.com" target="_blank">dblaikie@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+Chandler, who made the change<br>+Hans, who released the compiler<br><br>I'm really not sure what the right answer is here, though I don't know that much about releasing software & dependencies (whether they can be made dynamically optional, etc)</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 11:16 AM, Perry Hung <span dir="ltr"><<a href="mailto:perry@leaflabs.com" target="_blank">perry@leaflabs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>I'm using the official 3.6 release binaries for x64 Linux. When compiling with warnings, I don't see any color diagnostics. Explicitly enabling -fcolor-diagnostics works fine. I have TERM set to xterm-256color. Any idea why?</div><div><br></div><div>For what it's worth, I tried compiling LLVM/clang from trunk and color diagnostics work fine by default.</div><div><br></div><div>Upon further investigation, I saw that the official binaries were not linked against libtinfo:</div><div><br></div><div>Official binaries:</div><div><div>[14:11:05] perry@meepo ~/test </div><div>zsh▸ ldd /home/perry/opt/clang+llvm-3.6.0-x86_64-linux-gnu/bin/clang</div><div><span style="white-space:pre-wrap"> </span>linux-vdso.so.1 => (0x00007fff7c5fe000)</div><div><span style="white-space:pre-wrap"> </span>libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fbda8a56000)</div><div><span style="white-space:pre-wrap"> </span>libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fbda8852000)</div><div><span style="white-space:pre-wrap"> </span>libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fbda854b000)</div><div><span style="white-space:pre-wrap"> </span>libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fbda8247000)</div><div><span style="white-space:pre-wrap"> </span>libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fbda8031000)</div><div><span style="white-space:pre-wrap"> </span>libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fbda7c6b000)</div><div><span style="white-space:pre-wrap"> </span>/lib64/ld-linux-x86-64.so.2 (0x00007fbda8c99000)</div><div><br></div><div><br></div><div>Built from trunk:</div><div>[14:11:19] perry@meepo ~/test </div><div>zsh▸ ldd ~/src/llvm-git/build/bin/clang</div><div><span style="white-space:pre-wrap"> </span>linux-vdso.so.1 => (0x00007fffa4ffe000)</div><div><span style="white-space:pre-wrap"> </span>libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f146879d000)</div><div><span style="white-space:pre-wrap"> </span>libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007f1468574000)</div><div><span style="white-space:pre-wrap"> </span>libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f1468355000)</div><div><span style="white-space:pre-wrap"> </span>libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f146813c000)</div><div><span style="white-space:pre-wrap"> </span>libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1467e38000)</div><div><span style="white-space:pre-wrap"> </span>libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1467b31000)</div><div><span style="white-space:pre-wrap"> </span>libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f146791b000)</div><div><span style="white-space:pre-wrap"> </span>libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1467556000)</div><div><span style="white-space:pre-wrap"> </span>/lib64/ld-linux-x86-64.so.2 (0x00007f14689c6000)</div></div><div><br></div><div>Is this a build issue or user error?</div><div><br></div><div>thanks,</div><div>-perry</div></div>
<br>_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
<br></blockquote></div><br></div>
______________________________<u></u>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/<u></u>mailman/listinfo/llvmdev</a><br>
</blockquote></div>
</div></div></blockquote></div></div></div>
______________________________<u></u>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/<u></u>mailman/listinfo/llvmdev</a><br>
</blockquote></div></div>