On Tue, Jan 04, 2000 at 12:28:01AM -0500, Todd Suess wrote > I recently did a apt-get dist-upgrade on Jan 2nd, which updated ncurses to > version 5.0. I didn't notice any problems at first, but I went to build a > custom version of Nethack and noticed that it failed to compile with curses > errors. In examining the directorys, I found the following. During the > update > to curses5 all these links were changed in my /usr/include directory. > > lrwxrwxrwx 1 root root 11 Jan 2 20:54 curses.h -> > ../curses.h > lrwxrwxrwx 1 root root 8 Jan 2 20:54 eti.h -> ../eti.h > lrwxrwxrwx 1 root root 9 Jan 2 20:54 form.h -> ../form.h > lrwxrwxrwx 1 root root 9 Jan 2 20:54 menu.h -> ../menu.h > lrwxrwxrwx 1 root root 12 Jan 2 20:54 ncurses.h -> > ../ncurses.h > lrwxrwxrwx 1 root root 10 Jan 2 20:54 panel.h -> ../panel.h > lrwxrwxrwx 1 root root 9 Jan 2 20:54 term.h -> ../term.h > lrwxrwxrwx 1 root root 12 Jan 2 20:54 termcap.h -> > ../termcap.h > lrwxrwxrwx 1 root root 11 Jan 2 20:54 unctrl.h -> > ../unctrl.h > > All of these are broken symlinks, and with a little furthur testing I have > confirmed that no program that requires curses will now build sucessfully on > my > potato system. Has anyone else ran into this problem, and is there a > suggested fix? With so many programs using curses now days, this seems to be > a serious problem. >
Disclaimer: I'm running slink, and have never used the potato ncurses. In slink, /usr/include/ncurses is a symlink to '.'; if this is a real directory in the ncurses5 package and that package installs links to ../*.h in /usr/include/ncurses, you may get something like you describe. If you're feeling brave, try: # rm /usr/include/ncurses # dpkg -i /var/cache/apt/archives/ncurses5-dev*.deb Good luck, John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] "Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
