[Top][All Lists]

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

bug#10643: BUG REPORT libtool-2.4.2 Solaris 10 64bit - Update

From: Bob Friesenhahn
Subject: bug#10643: BUG REPORT libtool-2.4.2 Solaris 10 64bit - Update
Date: Mon, 30 Jan 2012 13:33:05 -0600 (CST)
User-agent: Alpine 2.01 (GSO 1266 2009-07-14)

On Mon, 30 Jan 2012, JONES, BILL wrote:

HOWEVER, once the first set of tests passed another section I have never seen before started...and it has failures also...I had to change all instances of configure in the directory tree, but still not all the tests passed...I sent the results of testsuite.log from the server with the bug# in the subject.

In test/cdemo/configure I see this code...so there IS a mechanism to detect which bit size being used. Could this be leveraged in the LD_LIBRARY_PATH section?

My preference is to find a way to remove any existing LD_LIBRARY_PATH_32 or LD_LIBRARY_PATH_64 definitions from the environment so that only LD_LIBRARY_PATH will be used. It does not seem to me that any LD_LIBRARY_PATH type variable set in the user's environment should be allowed to influence execution since libtool and its wrapper scripts are supposed to have full knowledge of the necessary linkage. Testing the linkage is important part of 'make check'. Is there a reason why this approach would be faulty?

Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

reply via email to

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