|
Line
Link Here
|
| 0 |
-- devmanual/ebuild-writing/common-mistakes/text.xml |
0 |
++ devmanual/ebuild-writing/common-mistakes/text.xml |
|
Lines 57-62
Link Here
|
| 57 |
</body> |
57 |
</body> |
| 58 |
</section> |
58 |
</section> |
| 59 |
|
59 |
|
|
|
60 |
<section> |
| 61 |
<title>Build log not verbose</title> |
| 62 |
<body> |
| 63 |
When writing ebuilds you should always check the build log, because the build |
| 64 |
system might ignore CC/CXX/LD/CFLAGS/LDFLAGS and such or add undesired flags |
| 65 |
by default. In order to analyze this and have complete information in case |
| 66 |
someone reports a bug for your package the <b>build log must always be verbose.</b> |
| 67 |
<p> |
| 68 |
There are several ways to fix non-verbose build logs depending on the build system: |
| 69 |
</p> |
| 70 |
<p> |
| 71 |
For <c>cmake</c> based build systems it should be sufficient that the ebuild calls |
| 72 |
cmake-utils_src_compile which picks up the cmake-utils.eclass variable 'CMAKE_VERBOSE=1' |
| 73 |
by default. If you call emake directly for whatever reason you can do 'emake VERBOSE=1' |
| 74 |
(note that cmake-utils_src_compile takes arguments as well which are passed to make). |
| 75 |
</p> |
| 76 |
|
| 77 |
<p> |
| 78 |
For <c>autotools</c> based build systems portage already passes '--disable-silent-rules' |
| 79 |
to econf. |
| 80 |
</p> |
| 81 |
|
| 82 |
<p> |
| 83 |
For custom Makefiles you probably have to write a patch. Try to get upstream to include an |
| 84 |
option like 'V=1' to enable full verbosity. |
| 85 |
</p> |
| 86 |
<note> If you notice non-verbose build log in any package open a bug and make it block the |
| 87 |
tracker bug #429308</note> |
| 88 |
</body> |
| 89 |
</section> |
| 90 |
|
| 60 |
</chapter> |
91 |
</chapter> |
| 61 |
|
92 |
|
| 62 |
</guide> |
93 |
</guide> |
