Date: Thu, 17 Jul 2003 18:40:27 -0400 (EDT) From: Kenneth Culver <culverk@yumyumyum.org> To: David O'Brien <obrien@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: problem after gcc import Message-ID: <20030717183959.H67799@alpha.yumyumyum.org> In-Reply-To: <20030717221725.GA55448@dragon.nuxi.com> References: <20030717160215.G67028@alpha.yumyumyum.org> <20030717221725.GA55448@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Read freebsd-current. :-) A suggestion was given this week: > > Subject: Re: Vim: Caught deadly signal BUS (after -current update with new gcc) > Date: Wed, 16 Jul 2003 23:14:30 -0700 > To: "Karel J. Bosschaart" <K.J.Bosschaart@tue.nl> > On Tue, Jul 15, 2003 at 11:07:40AM +0200, Karel J. Bosschaart wrote: > > FWIW, the new behaviour of vim is caused by patch 6.2.015. I added > > 015 to BADPATCHES in the ports Makefile and reinstalled. gvim works > > as usual now. > Ahh thanks, that'll teach me to let my "d"elete finger get away from me. :-P Ken
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030717183959.H67799>