Date: Fri, 09 Mar 2007 15:14:50 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Ade Lovett <ade@FreeBSD.org> Cc: Jean-Yves Lefort <jylefort@FreeBSD.org>, Kent Stewart <kstewart@owt.com>, freebsd ports <freebsd-ports@freebsd.org> Subject: Re: Ports 104877 causing big problems Message-ID: <45F1EA6A.6070904@FreeBSD.org> In-Reply-To: <BE66AB56-E0B4-420A-910D-9C10DB9AF24D@FreeBSD.org> References: <45F1DDE2.5030404@FreeBSD.org> <BE66AB56-E0B4-420A-910D-9C10DB9AF24D@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ade Lovett wrote:
>
> On Mar 09, 2007, at 14:21 , Doug Barton wrote:
>> Can we have some response from Ade, and/or portmgr on when this might
>> be fixed? I would agree that the current behavior is suboptimal.
>
> I'm pretty certain that this has been addressed with recent updates to
> devel/libtool15 and devel/libltdl15 -- certainly it solved the gnucash
> problem that had a similar failure case.
>
> The patch as it stands in 104877 is flawed in that it brings in
> bsd.autotools.mk merely with a GNU_CONFIGURE enabled and as such makes
> tree-wide changes to those ports that use this stanza, but not a
> USE_AUTOTOOLS stanza, thus giving no incentive for port maintainers
> themselves to ensure that the fixes are punted back upstream.
>
> So, item (1): does the problem actually still exist with a port using
> the in-tree devel/libtool15 (via USE_AUTOTOOLS= libtool:15[:env]. If
> yes, empirical evidence will be required as an addendum to the PR. If
> no, then we're done.
So it sounds like a reasonable way to proceed would be for Kent to
save a copy of his current libgpg-error +REQUIRED_BY file, then run
one of the commands that mezz suggested, and compare the before and
after pictures. If the problem is fixed, they should be substantially
different.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45F1EA6A.6070904>