Date: 24 Oct 2011 16:18:57 +0200 From: "John R. Levine" <johnl@iecc.com> To: freebsd-questions@freebsd.org Subject: Re: Updating emacs fails Message-ID: <alpine.BSF.2.00.1110241616280.65734@joyce.lan> In-Reply-To: <44y5wattox.fsf@be-well.ilk.org> References: <20111023071127.65536.qmail@joyce.lan> <4EA3C5A1.2080803@infracaninophile.co.uk> <alpine.BSF.2.00.1110231000080.42904@joyce.lan> <4EA3E3E3.5030806@infracaninophile.co.uk> <alpine.BSF.2.00.1110231709360.83309@joyce.lan> <44wrbv3bj9.fsf@lowell-desk.lan> <alpine.BSF.2.00.1110231800590.1924@joyce.lan> <44y5wattox.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Yes, that's just what I did, and I got an emacs that was linked against > the port version of ncurses. It worked fine. I deinstalled and rebuilt and reinstalled the ncurses port, and now emacs builds fine. Gaaah. I think the former version was the package that gets installed with 8.2, but reconstructing the former state would be a challenge. So, uh, I guess we chalk it up to bit rot. "Never mind." I have a couple of other ports that fail in similar ways, but I think I'll wiggle a few more moving parts before reporting the problem. Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1110241616280.65734>