Thanks for the reply. The patch to configure is essentially the same as one I applied. The Makefile is totally beyond my capabilities. :( It seems to rely on some kind of package system I have no knowledge of. -- Henry
2017-11-18 19:16 GMT+09:00 Carsten Mattner <carstenmatt...@gmail.com>: > Does this help you answer? > > https://github.com/DragonFlyBSD/DPorts/blob/master/sysutils/screen/Makefile > https://github.com/DragonFlyBSD/DPorts/blob/master/sysutils/screen/dragonfly/patch-configure > > On 11/18/17, Henry <nbsd4e...@gmail.com> wrote: >> I've seen references on the Internet to building screen with >> -lncursesw, but I can't seem to come up with the >> proper incantation. There was no clue in config.log to indicate why >> lncursesw was not picked up. >> Manually editing Makefile to force the use of -lncursesw yielded the >> errors: >> /usr/local/src/screen-4.6.2/display.c:715: undefined reference to `ospeed' >> /usr/local/src/screen-4.6.2/display.c:716: undefined reference to `tgoto' >> /usr/local/src/screen-4.6.2/display.c:716: undefined reference to `tputs' >> >> I was able to build screen by changing Makefile to read: >> CPPFLAGS = -I/usr/local/include -DETCSCREENRC='"$(ETCSCREENRC)"' \ >> -DSCREENENCODINGS='"$(SCREENENCODINGS)"' >> LDFLAGS = -L/usr/local/lib -L/usr/lib >> LIBS = -lncursesw -ltinfow -lelf -lutil -lcrypt >> >> Is this correct?? (especially the addition of -ltinfow) >> Is there someway to have the configure script create such a Makefile? >> >> Many TIA, >> Henry >> >> _______________________________________________ >> screen-users mailing list >> screen-users@gnu.org >> https://lists.gnu.org/mailman/listinfo/screen-users >> _______________________________________________ screen-users mailing list screen-users@gnu.org https://lists.gnu.org/mailman/listinfo/screen-users
