On Mon, Dec 26, 2005 at 08:15:56PM +0100, Mattia Dongili wrote:
> On Sat, Dec 24, 2005 at 02:38:11PM +0100, Kurt Roeckx wrote:
> > It's linking against the static libsysfs.a instead of against the
> > shared libsysfs.so.
>
> can't it be an issue in /lib vs /lib64 instead? Maybe libtool is trying
> to statically link because it can't find the shared object in /lib64
> (using /lib${libsuff} in the search path).
/lib64 is a symlink to /lib, so it should be able to find it
wether it's in using /lib or /lib64. And /usr/lib64 is a synlink
to /usr/lib.
> > After removing that from libcpufreq/aclocal.m4 and regenerating
> > the auto* files, it builds without problems.
>
> aren't there less instrusive measures? depending on libtool sucks.
> If my guess above is correct then you don't have /lib64, does linking
> /lib64 -> /lib helps (I'm not proposing it as a solution, I'd just like
> to confirm my idea, in that case I could use the LDFLAGS variable in
> debian/rules).
Since it's already the case, it's not going to help.
My guess is that it's removing paths it should contain, like some
gcc things.
I've already mailed both gentoo and and upstream libtool about
it, but I didn't get a response yet.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
