[gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/

public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed

From: "Markos Chandras" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/
Date: Wed,  8 Aug 2012 19:20:28 +0000 (UTC)	[thread overview]
Message-ID: <1344453604.a3ac99ece5056880cb0ad1a64ef39d59b574af7d.hwoarang@gentoo> (raw)

commit:     a3ac99ece5056880cb0ad1a64ef39d59b574af7d
Author:     Julian Ospald <hasufell <AT> gentoo <DOT> org>
AuthorDate: Sat Aug  4 00:33:15 2012 +0000
Commit:     Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Wed Aug  8 19:20:04 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=a3ac99ec

devmanual

document necessity to force all build logs verbose

---
 ebuild-writing/common-mistakes/text.xml |   31 +++++++++++++++++++++++++++++++
 1 files changed, 31 insertions(+), 0 deletions(-)

diff --git a/ebuild-writing/common-mistakes/text.xml b/ebuild-writing/common-mistakes/text.xml
index d2f5fcf..fb4f0d2 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -57,6 +57,37 @@ elog "They are listed in the INSTALL file in /usr/share/doc/${PF}"
 </body>
 </section>
 
+<section>
+<title>Build log not verbose</title>
+<body>
+When writing ebuilds, you should always check the build log, because the build
+system might ignore CC/CXX/LD/CFLAGS/LDFLAGS and such or add undesired flags
+by default. In order to analyze this and have complete information, in case
+someone reports a bug for your package, the <b>build log must always be verbose.</b>
+<p>
+There are several ways to fix non-verbose build logs depending on the build system:
+</p>
+<p>
+For <c>cmake</c> based build systems it should be sufficient that the ebuild calls
+cmake-utils_src_compile which picks up the cmake-utils.eclass variable 'CMAKE_VERBOSE=1'
+by default. If you call emake directly for whatever reason, you can do 'emake VERBOSE=1'
+(note that cmake-utils_src_compile takes arguments as well which are passed to make).
+</p>
+
+<p>
+For <c>autotools</c> based build systems you can pass '--disable-silent-rules' to econf
+until a new EAPI does that automatically. 'emake V=1' should also work.
+</p>
+
+<p>
+For custom Makefiles you often have to write a patch. Try to get upstream to include an
+option like 'V=1' to enable full verbosity.
+</p>
+<note> If you notice non-verbose build log in any package open a bug and make it block the
+tracker bug #429308</note>
+</body>
+</section>
+
 </chapter>
 
 </guide>

next             reply	other threads:[~2012-08-08 19:20 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 19:20 Markos Chandras [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-24 14:15 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/ Ulrich Müller
2022-01-22 23:43 Sam James
2021-12-22 15:38 Ulrich Müller
2021-09-17  9:09 Ulrich Müller
2021-08-14 10:00 Ulrich Müller
2021-08-01  2:43 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-03-30 18:20 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-21  6:06 Ulrich Müller
2021-02-06 10:35 Ulrich Müller
2017-01-25  5:31 Göktürk Yüksek
2017-01-25  5:31 Göktürk Yüksek
2017-01-21 19:21 Göktürk Yüksek
2016-10-28 17:13 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2014-10-18 17:36 Markos Chandras
2014-05-13 19:32 Ulrich Müller
2013-09-28 12:19 Markos Chandras
2012-12-30 14:21 Julian Ospald
2012-12-04 19:26 Julian Ospald
2012-11-23 18:02 Julian Ospald
2012-11-17 19:00 Markos Chandras
2012-11-11 19:33 Markos Chandras
2012-11-07 13:27 Michael Palimaka
2012-11-07 13:25 Michael Palimaka
2011-03-09 16:42 Jeremy Olexa

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:d2f5fcf dfblob:fb4f0d2 )
 OR (
bs:"[gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/" )
	(help)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1344453604.a3ac99ece5056880cb0ad1a64ef39d59b574af7d.hwoarang@gentoo \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Be sure your reply has a Subject: header at the top and a blank line before the message body.

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox