Date: Sat, 7 Aug 2004 20:40:26 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Dwayne MacKinnon <Dwayne.MacKinnon@xwave.com> Cc: ports@FreeBSD.org Subject: Re: Problem with vim-6.3.15 Message-ID: <20040808034026.GB53594@dragon.nuxi.com> In-Reply-To: <4113A0AB.2030409@xwave.com> References: <4113A0AB.2030409@xwave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 06, 2004 at 11:15:55AM -0400, Dwayne MacKinnon wrote: > I did some web research on rcmdsh and vim (my first thought was that > someone had somehow inserted a trojan into vim :-) and found that this > sort of thing had happened before. The explanation, given by Kris > Kennaway, is that the binary had somehow been linked to both libc and > libc_r. I used ldd to check my vim binary, and sure enough, linked to both. ... > I'm on 4.10-RELEASE, btw. I wonder there may be a problem with ports/Mk/bsd.port.mk trying to support both 4.x and 5.x at the same time. I really don't have any 4.x development systems any more, so this isn't something I can look into. If you figure out what is going on and can send patches, that I something I can act on. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040808034026.GB53594>