Francesco Namuri <[EMAIL PROTECTED]> writes: > I'm thinking this because after the call of ./configure the generated > libtool file contains all the lib variables set to corresponding lib64 > directory eg (after a call of ./configure):
Yeah, that's broken, don't do that. /usr/lib is the library path on Debian's AMD64 build. Upstream is probably being too smart for their own good somewhere and setting libdir to lib64. (Red Hat tends to force this, unfortunately.) You could try using --libdir=/usr/lib and seeing if that overrides things. > So I thought that are the problem is related to the symlink... The problem is that libtool doesn't think that lib64 is on the regular library search path and hence decides that it needs to add rpath, which is broken at several different levels but best avoided by just using lib. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
