Bug 451820 – sys-libs/libseccomp has not verbose build log

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Agostino Sarubbo 2013-01-13 17:20:13 UTC]

The proposed solution is in the tracker.
If this is an autotools based package, and '--disable-silent-rules' doesn't work, you can try:
- emake V=1 in src_compile() and/or src_install()
- MAKEOPTS+=" V=1" as global scope

Note: if you will port the ebuild to EAPI 5, it includes '--disable-silent-rules'

[Comment 1 Paul Moore 2013-06-17 19:37:36 UTC]

I updated my own private ebuild for sys-libs/libseccomp to match the new upstream version and added the bits for a verbose build.  See the ebuild attached to BZ #473626.

* https://473626.bugs.gentoo.org/attachment.cgi?id=351264

[Comment 2 Paul Moore 2013-06-17 19:57:01 UTC]

(In reply to Paul Moore from comment #1)
> I updated my own private ebuild for sys-libs/libseccomp to match the new
> upstream version and added the bits for a verbose build.  See the ebuild
> attached to BZ #473626.
> 
> * https://473626.bugs.gentoo.org/attachment.cgi?id=351264

Minor typo correction to the ebuild posted above (problem in the install phase):

* https://473626.bugs.gentoo.org/attachment.cgi?id=351268

[Comment 3 SpanKY 2013-06-17 20:41:26 UTC]

just reference the bug rather than the attachment

[Comment 4 SpanKY 2013-06-18 03:58:40 UTC]

should be all set now in the tree; thanks for the report!

Commit message: Set V=1 when building
http://sources.gentoo.org/sys-libs/libseccomp/libseccomp-2.1.0.ebuild?rev=1.1