[LLVMdev] Color diagnostics
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:
> 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
> 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
>> > with warnings, I don't see any color diagnostics. Explicitly enabling
>> > -fcolor-diagnostics works fine. I have TERM set to xterm-256color. Any
>> > 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
>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev