[LLVMdev] Color diagnostics

Chandler Carruth chandlerc at google.com
Mon Mar 30 15:28:43 PDT 2015


On Mon, Mar 30, 2015 at 6:27 PM Perry Hung <perry at leaflabs.com> wrote:

> Hi Hans,
>
> I used the official Ubuntu binary:
>
> http://llvm.org/releases/3.6.0/clang+llvm-3.6.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz
>
> Seems to me that it should be an optional dependency. If the target system
> has tinfo or ncurses, it should use it, otherwise fallback to no color.
>

There is no reasonable way to implement that IMO. It would require using
dlopen to test for the library, open up a world of security and performance
concerns, etc.



>
> On Mon, Mar 30, 2015 at 6:02 PM, Hans Wennborg <hans at chromium.org> wrote:
>
>> Hi Perry,
>>
>> On Mon, Mar 30, 2015 at 11:16 AM, Perry Hung <perry at leaflabs.com> wrote:
>> > 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?
>>
>> Which of the release binaries are you using? 3.6 has x86_64 binaries
>> for Ubuntu, OpenSuSE and Fedora, and they were built by difference
>> people.
>>
>> From your ldd dump, it seems the binary you're using was built without
>> libtinfo, presumably because it wasn't installed on that machine and
>> we don't require it for building.
>>
>>  - Hans
>>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150330/1194ca22/attachment.html>


More information about the llvm-dev mailing list