libtool
[Top][All Lists]
Advanced

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

Re: (With Patch) Re: DESTDIR trouble


From: Bernd Jendrissek
Subject: Re: (With Patch) Re: DESTDIR trouble
Date: Tue, 8 Jul 2003 08:32:52 +0200

On Mon, Jul 07, 2003 at 08:42:14PM -0400, Charles Wilson wrote:
> Alexandre Duret-Lutz wrote:
> 
> > 
> >  R> For several _YEARS_, packagers for software were very troubled because
> >  R> of not-completely-working staging install. I really hope this issue can
> >  R> be sorted out, once and for all.
> > 
> > One way to address the "once for all" part would be to write a
> > test case.
> 
> I don't think this ia test case that can be made part of the testsuite, 
> unfortunately.
> 
> The problem is, you ONLY see the problem if all of the following are true:
> 
> 1) you have multiple dependent constructs in a single project -- e.g. a 
> sharedlib and an executable that depends on it, or two sharedlibs where 
> one depends on the other, etc.
> 
> 2) you are doing a DESTDIR install
> 
> 3) you have PREVIOUSLY done a "real" install -- so that the sharedlib on 
> which the second construct depends already exists in the "final" 
> destination.
> 
> Then, relinking will pick up the pre-existing sharedlib in the "final" 
> location, rather than the one in the DESTDIR.
> 
> In order to make #3 true, you have to muck with things "outside" of the 
> testsuite tree...which kinda violates the whole premise of 
> self-contained testing.

I imagine the testsuite could demand that destdir-relink-demo's libone and
libtwo are already installed.  If not, the test case just exits with code
77 - the test can't run.

AC_CHECK_LIB(one, one_set_global_int_var, [true], [exit 77])

> But, if anyone would like to give it a try, they are welcome to adapt 
> any of the following standalone testcase if it is useful.
> http://mail.gnu.org/archive/html/libtool/2003-05/msg00022.html




reply via email to

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