From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SEph4-0002JV-RT for garchives@archives.gentoo.org; Mon, 02 Apr 2012 22:25:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C9D3FE0B76; Mon, 2 Apr 2012 22:25:32 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id BE751E0B51 for ; Mon, 2 Apr 2012 22:24:36 +0000 (UTC) Received: from [192.168.1.204] (133.150.222.87.dynamic.jazztel.es [87.222.150.133]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id A5B431B402B for ; Mon, 2 Apr 2012 22:24:35 +0000 (UTC) Subject: Re: [gentoo-dev] Re: [RFC] enable verbose build whenever it's possible From: Pacho Ramos To: gentoo-dev@lists.gentoo.org In-Reply-To: <20111105210307.570e6c52@gentoo.org> References: <4EB4FA98.3080201@gentoo.org> <201111052100.32508.reavertm@gmail.com> <20111105210307.570e6c52@gentoo.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-jc5KV1ULNMAxdmfTk4fg" Date: Tue, 03 Apr 2012 00:24:32 +0200 Message-ID: <1333405472.10130.5.camel@belkin4> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 X-Archives-Salt: a2d4e5b1-040d-4280-8f71-45cf28ee6613 X-Archives-Hash: eacfc7b5545c19db972925ed32faf467 --=-jc5KV1ULNMAxdmfTk4fg Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El s=C3=A1b, 05-11-2011 a las 21:03 -0600, Ryan Hill escribi=C3=B3: > On Sat, 5 Nov 2011 21:00:32 +0100 > Maciej Mrozowski wrote: >=20 > > > I've seen too many bugs reports today that gave me cute, colorful > > > build.logs and almost no information about underlaying bug... > >=20 > > That's usually because users sometimes attach only "relevant" parts of = build=20 > > log (well, relevant according to their taste =3D last lines, even when = they use=20 > > parallel compilation). >=20 > I think you're confusing build log with build output. >=20 > > Any particular example of bug report with entire build log from cmake-u= tils in=20 > > fancy mode, and still being unable to locate the problem? > >=20 > > I ask, because we're appending summary just after configure phase to ma= ke=20 > > vorbose logging of whole build process unecessary. >=20 > How are you supposed to debug a compile or linker error without the compi= ler > command line? >=20 >=20 How all this ended up? It would still be nice to have verbose output enabled by default (even people being able to use emerge --quiet to silent it) to check for undesired flags (like -Werror, -DG_DISABLE_DEPRECATED...) easily :) --=-jc5KV1ULNMAxdmfTk4fg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk96JyAACgkQCaWpQKGI+9QQYQCeOyKjUbkoWDQEwXBaVDKlmpLC pl0An0bw8KYUR1HlRj6maEYdbR08ECfn =NF5j -----END PGP SIGNATURE----- --=-jc5KV1ULNMAxdmfTk4fg--