On Thu, Nov 16, 2006 at 01:51:58PM +0900, Henry Nelson wrote: > On Wed, Nov 15, 2006 at 03:27:23PM +0100, Michael Schroeder wrote: >> Could be a bug in screen's utmp handling. What OS are you running? > > % uname -sr > NetBSD 3.0.0_STABLE > % screen -v > Screen version 4.00.02 (FAU) 5-Dec-03 > % gcc -v > gcc version 3.3.3 (NetBSD nb3 20040520) > > I build Screen statically linked: > % setenv CFLAGS "-O2" > % setenv LIBS "-static -lncursesw" > % setenv LDFLAGS "-L/usr/local/lib -lncursesw" > % ./configure --prefix=/usr/local --disable-socket-dir --enable-colors256
Are you building screen out of pkgsrc? or straight from the tarball? I'm running a similar setup (NetBSD-3.0/i386), but I always build screen out of pkgsrc and don't have that problem. A quick grep of the patches that get applied when using the pkgsrc version shows a lot of references to getutent/utmpx fixes -- Michael Parson [EMAIL PROTECTED] _______________________________________________ screen-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/screen-users
