Date: Wed, 16 Jul 2003 23:14:30 -0700 From: "David O'Brien" <obrien@freebsd.org> To: "Karel J. Bosschaart" <K.J.Bosschaart@tue.nl> Cc: current@freebsd.org Subject: Re: Vim: Caught deadly signal BUS (after -current update with new gcc) Message-ID: <20030717061430.GB96381@dragon.nuxi.com> In-Reply-To: <20030715090740.GA77879@phys9911.phys.tue.nl> References: <200307142038.h6EKciQ06885@mailgate5.cinetic.de> <20030714204643.GA14890@titan.klemm.apsfilter.org> <20030715090740.GA77879@phys9911.phys.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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. I'm willing to commit it as such, but I'd like to hear more people's opinion. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030717061430.GB96381>