<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 19, 2013, at 10:43 PM, Randolph D Dach wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">It seems the python-64 is going to the wrong set of libraries, should be going after the /usr/lib64/python2.7 libraries. <br>If I use ldd -v /usr/lib/python2.7/lib-dynload/_struct.so it returns showing /usr/lib and /lib libraries<br>if I use ldd -v /usr/lib64/python2.7/lib-dynload/_struct.so it returns /usr/lib64 and /lib64 libraries.</span></blockquote></div><br><div>Python isn't a very multilib friendly package. What we have up in CBLFS is pretty much a difficult hack and still problems exist.</div><div>Could always go back to the old version which didn't seem to have many problems!</div><div><br></div><div>Sincerley,</div><div><br></div><div>William Harrington</div></body></html>