<html>
<head>
<base href="http://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 --- - python site-packages is installed into "lib64" (not "lib") on RedHat 64-bit linux."
href="http://llvm.org/bugs/show_bug.cgi?id=18957">18957</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>python site-packages is installed into "lib64" (not "lib") on RedHat 64-bit linux.
</td>
</tr>
<tr>
<th>Product</th>
<td>lldb
</td>
</tr>
<tr>
<th>Version</th>
<td>3.4
</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>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>All Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>lldb-dev@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Reporter</th>
<td>triple.yang@gmail.com
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>There is incompatibility about python site-packages on my 64-bit RedHat
Enterprise Linux 6.3, so lldb can not run "script" command properly because it
can not search python libraries.
Problem 1: $(framework_python_dir) is evaluated as
"....../lib64/python2.6/site-packages" in shell script
"finish-swig-Python-LLDB.sh" and later a soft link named "_lldb.so" pointing to
../../../liblldb.so is created. Since lldb puts liblldb.so into "lib", this
soft link is broken. The correct soft link might be
"../../../../lib/liblldb.so".
Problem 2: lldb always install python into system path
/usr/lib64/python2.6/site-packages. If we do not has the authority, installment
will fail.
Problem 3 (possible): Assume we change finish-swig-Python-LLDB.sh to install
python2.6/site-packages into $(LLVM_Install_Path)/lib64 (which is natual in
finish-swig-Python-LLDB.sh), lldb still can not find python dependencies since
Host::GetLLDBPath() in lldb/source/Host/common/Host.cpp detects
g_lldb_python_dir at "....../lib/python". I believe current implementation does
not distinguish 64-bit and 32-bit linux OSes.
In a word, since python is defaulted to be installed at "/usr/lib64/......"
instead of "/usr/lib/......" on my 64-bit RHEL, lldb can not run "script".</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>