<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW " title="NEW --- - building rpm will include upward workspace directory" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__llvm.org_bugs_show-5Fbug.cgi-3Fid-3D23843&d=AwMBaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=pF93YEPyB-J_PERP4DUZOJDzFVX5ZQ57vQk33wu0vio&m=QAL-JGlX-FxTHJte1B1lNTmF0nvHwi6e0etJ2Phg1hE&s=Wmape_BbCriUGuQoqVBoVHAP_nYJJZx46Wu83YBAvTs&e=">23843</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>building rpm will include upward workspace directory
</td>
</tr>
<tr>
<th>Product</th>
<td>Build scripts
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>cmake
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>tps@vr-web.de
</td>
</tr>
<tr>
<th>CC</th>
<td>llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>If you set up
/var/lib/jenkins/sharedspace/llvm/llmv/<all-llvm-source>
/var/lib/jenkins/sharedspace/build
then
cd /var/lib/jenkins/sharedspace/build
cmake -G "Unix Makefiles" ../llvm
make
cpack -D CPACK_RPM_PACKAGE_DEBUG=1 -D CPACK_RPM_SPEC_INSTALL_POST="/bin/true"
-G RPM
will include /var/lib/jenkins into the rpm (no files, only the directory).
installing build rpm leads to an error:
rpm -vhU /var/lib/jenkins/sharedspace/llvm/build/LLVM-3.7.0svn-Linux.rpm
Vorbereiten... ########################################
Datei /var/lib/jenkins aus der Installation von llvm-3.7.0svn-1.x86_64
kollidiert mit der Datei aus dem Paket jenkins-1.617-1.1.noarch
If installed on a system without jenkins, install runs fine, but creates an
empty directory "/var/lib/jenkins".
At some point the procedures include, in all cases, a directory "../.." up from
the build-directory. The most bad thing: this directory might be removed
completely in case of deinstalling with option --purge given. If your build
directory is "/xxy/xxz" you end up with "/" deleted (but you have to be really
ignorant to achieve this ;-)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>