[Top][All Lists]

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

Re: The newly built is never used for "make check"

From: H. J. Lu
Subject: Re: The newly built is never used for "make check"
Date: Fri, 3 Sep 2004 15:12:59 -0700
User-agent: Mutt/1.4.1i

On Fri, Sep 03, 2004 at 01:51:34PM -0700, H. J. Lu wrote:
> The newly built may not be used for "make check". It
> leads to 2 problems:
> 1. The newly built may be fully tested by "make check".
> 2. Those tests which won't work with old may fail.
> This patch
> tries to fix PR 16633. There is another bug
> Could someone please review my patch?

PR 17311 has something do to with libtool which can't handle mixed
shared libraries built with and without libtool. In this case, the
shared libgcj is built with libtool and isn't. gij is
linked with both libgcj and When gij is run during
"make check", the build directory of libgcj is put into DT_RPATH
of lt-gij before the install directory while the build directory of isn't. As the result, if there is an installed, it will be used by lt-gij. Setting LD_LIBRARY_PATH won't
change it.

There is a libtool bug. I don't see why libtool should leave the
install directory in DT_RPATH for lt-xxx at all. It works if all
shared libraries are built with libtool. But it isn't the case
for gcc.


reply via email to

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