Date: Mon, 24 Oct 2011 09:17:34 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: "John R. Levine" <johnl@iecc.com> Cc: freebsd-questions@freebsd.org Subject: Re: Updating emacs fails Message-ID: <44y5wattox.fsf@be-well.ilk.org> In-Reply-To: <alpine.BSF.2.00.1110231800590.1924@joyce.lan> (John R. Levine's message of "23 Oct 2011 18:03:10 %2B0200") 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>
next in thread | previous in thread | raw e-mail | index | archive | help
"John R. Levine" <johnl@iecc.com> writes: >>>> On 23/10/2011 09:03, John R. Levine wrote: >>>>>> checking for tparm in -lncurses... no >>>>>> >>>>>> but that's not correct. libncurses should certainly contain that >>>>>> symbol. I get a 'yes' there on my stable/8 machine. As -lncurses is >>>>>> part of your LDFLAGS ... hmmm... do you have libncurses on your system >>>>>> anywhere other than in /lib ? >>>>> >>>>> I have the ncurses-5.9 package installed from ports. Several gnome >>>>> programs depend on it: >>>>> >>>>> pkg_delete: package 'ncurses-5.9' is required by these other packages >>>>> and may not be deinstalled: >>>>> aalib-1.4.r5_6 >>>>> gnome-games-2.32.1_2 >>>>> guile-1.8.8 >>>>> libcdio-0.82_2 >>>>> libxine-1.1.19_7 >>>> >>>> Interesting. Can you try moving /usr/local/lib/libncurses.* and >>>> /usr/local/include/ncurses.h aside temporarily and then rebuild emacs? >>>> If that works, then looks like you've found a bug in the editors/emacs >>>> port, which should be reported to the port's maintainer. >>> >>> Yup, that fixed it. I'll file a bug report. I tried rebuilding some >>> of the packages that allegedly depend on the ncurses port, and they >>> all seemed to work OK, so the right solution may be to deprecate the >>> ncurses port or fold it into the mainline system. >> >> The way it's supposed to work is that emacs will depend on (and link to) >> ncurses if it's installed when the emacs port is built, and to the base >> system curses if not. I just did a quick test, and this was just what >> did happen. So at least part of the problem is local to your system... > > Did you try installing the ncurses port and then rebuilding emacs? For > some reason the library in the ncurses port doesn't define the termcap > routines, leading to the problem. 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 then deleted the ncurses port to make sure emacs *really* was using ncurses from the port, and, indeed, emacs stopped working. > This computer has an extremely vanilla install of 8.2 with gnome. I'm > having trouble figuring what I'm doing different from anyone else > other than perhaps doing portupgrade more often than others do. I do it pretty often myself...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44y5wattox.fsf>