[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how to debug unexpected dependency

From: Ralf Wildenhues
Subject: Re: how to debug unexpected dependency
Date: Thu, 27 Jan 2011 19:29:14 +0100
User-agent: Mutt/1.5.20 (2010-08-04)

Hello Mirko,

* Mirko Vukovic wrote on Thu, Jan 27, 2011 at 06:31:04PM CET:
> A build of mpc on 64-bit RHEL5 fails.  I tracked down the cause to an entry
> in file:
> # Libraries that this one depends upon.
> dependency_libs='
> /usr/local/lib/
> /usr/local/lib/'

> I am looking for ideas on how to debug this condition.

Usually, by looking at the output of the 'libtool --mode=link' command
that produces this library, with --debug added as first argument to
libtool.  In this (usually large!) trace output find out why this path
is searched at all.  That usually points to where the problem comes from.

If you have the trace but cannot decipher it, feel free to post it here,

Hope that helps.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]