bug-libtool
[Top][All Lists]
Advanced

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

Re: [libtool 2.2.6b] testsuite: 46 failed


From: Ralf Wildenhues
Subject: Re: [libtool 2.2.6b] testsuite: 46 failed
Date: Sat, 20 Feb 2010 09:46:50 +0100
User-agent: Mutt/1.5.20 (2009-10-28)

Hello Konstantinos, Nathan,

first off, thanks for the bug report, even if FSF libtool is not
affected, and thanks for tracking upstream bug reports.

* Nathan Phillip Brink wrote on Fri, Feb 19, 2010 at 05:24:34PM CET:
> On Fri, Feb 19, 2010 at 11:04:18AM +0200, Konstantinos Bekiaris wrote:
> > i tried to update the whole system of my Gentoo machine, and i get
> > the
> Have you filed a bug at https://bugs.gentoo.org/ or checked if one
> exists already? A quick search shows me https://bugs.gentoo.org/293758
> which matches the error below:
> 
> >  46: lt_dlopen archive                               FAILED 
> > (lt_dlopen_a.at:95)
> 
> Such problems should be addressed and reported to this list only by
> Gentoo devs since Gentoo patches libtool ;-). I would recommend CC-ing
> yourself on that bug so you are informed when it is fixed. Also, you
> may temporarily disable running tests using FEATURES=-test. Or you
> could try the workaround posted on the bug to do something like
> FEATURES=-sandbox emerge -1v libtool

Well, if distributions patch libtool, we would be interested to know
about it: we care about not having diverging packages.  Moreover, we
get bug reports from users on one system that are caused by changes to
libtool an another system by the developer making the package.

It would be good if the modified package were easily identifiable as
such.  I'm not sure whether we need to change any code for that, but
even if we don't, we don't document for distributors how to do it.

Cheers,
Ralf




reply via email to

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