From owner-freebsd-ports@FreeBSD.ORG  Fri Feb  8 19:17:05 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id F0CBE26D
 for <ports@freebsd.org>; Fri,  8 Feb 2013 19:17:05 +0000 (UTC)
 (envelope-from utisoft@gmail.com)
Received: from mail-ie0-x230.google.com (ie-in-x0230.1e100.net
 [IPv6:2607:f8b0:4001:c03::230])
 by mx1.freebsd.org (Postfix) with ESMTP id C78A99E4
 for <ports@freebsd.org>; Fri,  8 Feb 2013 19:17:05 +0000 (UTC)
Received: by mail-ie0-f176.google.com with SMTP id k13so5357172iea.7
 for <ports@freebsd.org>; Fri, 08 Feb 2013 11:17:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=x-received:mime-version:sender:in-reply-to:references:from:date
 :x-google-sender-auth:message-id:subject:to:cc:content-type;
 bh=KwgBXR204uIVQgkN68/0GXTJ7D0m+CwDG3PwzihWheI=;
 b=h23EnqOlN4fgUAnrw48CZK+blo8cysfEV7PhAu8L26j5vNCoj8dpjs4WP7KE7cJZQY
 LQGm8F8+k/WySgObB/Y8C/UhcaJJE4ilW/xr105Mvq4mqj4LTbKVFApr0Ta5UkijMGQG
 SvRpa26iITknOyBehPDqjGxMYJSYwUltv4kCm2p9Q43aK5mMhyKGtbwReNDqCF2pXjOG
 sTRfaEe74tiMFQ0Lb4f9QKIwp7pk5xyk11J+tBVngIt5LWU8DUUSTdWnP9J+cQzW639Z
 /IZ8a2dL+xbvMcVjqHBUfKJA3hQVDzNOYMUWW03mnlKD+aGtc/L+IgeLQ5/OtjlvgHOW
 YEqQ==
X-Received: by 10.50.202.97 with SMTP id kh1mr4833437igc.15.1360351025472;
 Fri, 08 Feb 2013 11:17:05 -0800 (PST)
MIME-Version: 1.0
Sender: utisoft@gmail.com
Received: by 10.64.16.73 with HTTP; Fri, 8 Feb 2013 11:16:35 -0800 (PST)
In-Reply-To: <510F45F0.5050205@rawbw.com>
References: <510DE42F.40207@rawbw.com>
 <CADLo83_Ckvc9JsLkWG-e7PoV5_7uf256Me843w_Wdcf87nLNZA@mail.gmail.com>
 <510F45F0.5050205@rawbw.com>
From: Chris Rees <crees@FreeBSD.org>
Date: Fri, 8 Feb 2013 19:16:35 +0000
X-Google-Sender-Auth: YEpI7PyOB2O_mBUFEaZOXPwpldg
Message-ID: <CADLo838V9kLkUK-vLh+_NLCM=zOqt5TiHfn=ryN0_yp2V88BqA@mail.gmail.com>
Subject: Re: Why the port build log file has terminal escape sequences?
To: Yuri <yuri@rawbw.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ports@freebsd.org" <ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Feb 2013 19:17:06 -0000

On 4 February 2013 05:24, Yuri <yuri@rawbw.com> wrote:
> On 02/03/2013 03:13, Chris Rees wrote:
>>
>> I guess this is a cmake/clang port?  Cmake, clang and several other
>> tools give colorised output.  This is achieved with escape sequences.
>
>
> I understand about colorized output.
> But aren't such tools normally expected to turn colors off when run not in
> terminal?
> This is achieved by checking isatty (ttyname(3)).
> Probably I should file such PR to cmake. This might be a regression there.
>

Best check it really is a cmake bug, but it wouldn't go amiss.

Chris