ReleaseEngineering/PuppetAgain/HowTo/Build RPMs: Difference between revisions

ReleaseEngineering/PuppetAgain/HowTo/Build RPMs (view source)

243 bytes added , 8 October 2014

Confirmed users

107

edits

@@ Line 47: / Line 47: @@
 * If necessary, fetch the .src.rpm you built earlier.
-* Execute these steps to build:
+* Execute these steps to build for both 32 and 64 bit packages:
 <pre>
+$ # 64 bit:
 $ rm -rf /var/cache/mock/epel-6-x86_64/ccache
-$ mock --rebuild -r puppetagain-centos6-64 mozilla-python27-2.7.3-0.el6.src.rpm
+$ $ mock --rebuild -r puppetagain-centos6-64 mozilla-python27-2.7.3-0.el6.src.rpm
+$
+$ # 32 bit:
+$ rm -rf /var/cache/mock/epel-6-i386/ccache/
+$ mock --rebuild -r puppetagain-centos6-32 mozilla-python27-2.7.3-0.el6.src.rpm
 </pre>
 The script will tell you where the results are available.
-Use '-r puppetagain-centos6-32' instead to build a 32-bit package.
+If your build fails with something like "configure: error: cannot compute suffix of object files: cannot compile" in /var/lib/mock/epel-6-x86_64/result/build.log, or error messages complaining of a permission denied for /tmp/ccache/0/0 folder, it probably means that the last person to build an rpm didn't do the 'rm -rf' cleanup step. You'll need to do it as root:
-If your build fails with something like "configure: error: cannot compute suffix of object files: cannot compile" in /var/lib/mock/epel-6-x86_64/result/build.log, it probably means that the last person to build an rpm didn't do the 'rm -rf' cleanup step. You'll need to do it as root:
 <pre>
 $ su -
 (slave root password)
+# rm -rf /var/cache/mock/epel-6-i386/ccache/
 # rm -rf /var/cache/mock/epel-6-x86_64/ccache
 </pre>