From owner-freebsd-questions@FreeBSD.ORG Sun Jan 23 23:29:04 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A064A106564A for ; Sun, 23 Jan 2011 23:29:04 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 638AC8FC08 for ; Sun, 23 Jan 2011 23:29:04 +0000 (UTC) Received: by iwn39 with SMTP id 39so3554143iwn.13 for ; Sun, 23 Jan 2011 15:29:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=u/L8ZfDm+yGCiYQm+HEtp6GSi1byMm0tfmJ29PO9GA8=; b=iaSCx0YlBAv4HV2CmCDfUrxb7wsvE3pow5uTukU8Us1fBRcWv6YLeDqZtzo95sRd/a sa+EkZLmpGjFJmQZm+rTaK5jJkssictATRXFNF0UG8yWOUtoH9lXYqWc2lQ3Gl9Rufgh OUfp2pe/kZDTjhO+kNAHo8pOOZ5OUhwV4U6v0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=kfwGS36YVUssSUD0cpXWG6o/4NevqinNUC5WByDM3DuhBClD3/Oe5caxsokybch+In f7LGnB1MSR5iIbdhaZKi0X4phe9+O8AJ9DB/H5Vtp8rFHQEqfEPT471Cee2OVz3fNprb OBasU9uaZ3ZXUAlU+1NvqP7eRTSt5EqG0FPoU= Received: by 10.42.175.3 with SMTP id ay3mr2579770icb.13.1295823983201; Sun, 23 Jan 2011 15:06:23 -0800 (PST) Received: from mark-debian.phub.net.cable.rogers.com (CPE00044b162033-CM00111ae61918.cpe.net.cable.rogers.com [99.236.163.170]) by mx.google.com with ESMTPS id he5sm9385588icb.10.2011.01.23.15.06.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 23 Jan 2011 15:06:21 -0800 (PST) Date: Sun, 23 Jan 2011 18:07:33 -0500 From: Mark Johnston To: "Michael D. Norwick" Message-ID: <20110123230733.GA24421@mark-debian.phub.net.cable.rogers.com> References: <4D3B8BD4.5010606@centurytel.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D3B8BD4.5010606@centurytel.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-questions@freebsd.org Subject: Re: Colorized compiler/linker messages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2011 23:29:04 -0000 On Sat, Jan 22, 2011 at 08:00:52PM -0600, Michael D. Norwick wrote: > Good Day, > > I have seen this for some time when building ports and was wondering > how it was done. GCC when compiling and linking certain programs, > ebook for example, emits messages in various colors. How is that > done? Where does one find what the various colors are supposed to > signify? Or, is it just because it's more appealing? > > Thank You, > > Michael I'm not sure about ebook specifically, but there's a wrapper for gcc called colorgcc which colorizes the diagnostics and errors that gcc emits. The idea is that one can just do something like "CC=colorgcc make" when building. I'm sure there are other programs out there that do something similar, but colorgcc is the most common I think. Apparently there are similar wrappers for make and diff as well. -Mark