Message: previous - next
Month: April 2012

Re: [trinity-devel] python-tqt, python-trinity on 64-bit

From: "David C. Rankin" <drankinatty@...>
Date: Fri, 20 Apr 2012 21:40:45 -0500
On 04/20/2012 08:25 PM, Darrell Anderson wrote:
> Because lib64 is where the lib files belong. That is how things are done on 64-bit.
> Sym linking doesn't work and is an incorrect way of resolving the problem anyway.
> Darrell

Nope... 64 bit libs go just fine in 'lib', it's just a matter of choice. Unless
you are building both 64-bit apps and 32-bit apps in the same install - it
doesn't matter where they go as long as they can be found. On arch, all 64-bit
libs go in 'libs' and my stuff builds fine. On opensuse 64-bit libs go in lib64,
things build just fine there as well. So it's just a matter of choice, but it
has to be a consistent choice.

If you patched your tde build to put things in lib64 -- that's probably the
source of your issue. There is part of tde or tqt that doesn't know to look in
lib64. Just unpatch any of your tde files that you changed, and leave the libs
in lib and I'll bet your 64bit builds work fine.

I don't know where the flag is that controls where the build looks for libs, but
I think you hit it, and I don't know how to tell a python configure to search
for --with-extra-libs '/xyz', so I don't mess with it :)

David C. Rankin, J.D.,P.E.