Date: Sat, 11 Mar 2006 22:35:19 -0600 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Ade Lovett <ade@FreeBSD.org> Cc: ports@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Unable to build or update vcdimager Message-ID: <20060312043519.GB61472@over-yonder.net> In-Reply-To: <502E0068-C21A-4990-B588-07CB6E27C70B@FreeBSD.org> References: <20060310173657.Q40614@seibercom.net> <20060311153759.41c98e18.nork@FreeBSD.org> <20060311234731.GA91232@over-yonder.net> <200603112129.32522.gerard@seibercom.net> <20060312023201.GA61472@over-yonder.net> <502E0068-C21A-4990-B588-07CB6E27C70B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 11, 2006 at 08:29:36PM -0800 I heard the voice of Ade Lovett, and lo! it spake thus: > > Since libtool has precisely nothing to do with texinfo files, I'm > curious as to how you came to this co-incidental guess. libtool is > merely a wrapper around compiling and linking executable code and > libraries. Nothing more, nothing less. In that it's the only relatively major structural change in ports I'm aware of recently, and I had the same problem with 2 seemingly unrelated ports at the same time (earlier today, in fact) after pulling myself across that boundary, both of which use libtool. I have only the vaguest clue what libtool actually does; the two just seemed to come about at the same time. I've never seen the info errors before either, and I've built both ports before. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060312043519.GB61472>