The following reply was made to PR port-amd64/34282; it has been noted by GNATS.

From: Thomas Dickey <dickey@radix.net>
To: Alan Barrett <apb@cequrux.com>
Cc: gnats-bugs@NetBSD.org
Subject: Re: port-amd64/34282: console color is broken on amd64 when using pkgsrc/misc/screen on amd64
Date: Thu, 5 Oct 2006 06:51:42 -0400

 --liOOAslEiF7prFVr
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Thu, Oct 05, 2006 at 06:48:39AM +0000, Alan Barrett wrote:
 > On Wed, 04 Oct 2006, Thomas Dickey wrote:
 > >  However, none of the comments made on the mailing lists have
 > >  identified the problem other than the oblique comment that it has
 > >  been fixed in some version.
 > >  (Since no analysis has been presented, it is unlikely that it is fixed=
 ).
 >=20
 > Since the string "OOPS" no longer appears in the libterm sources, or in
 > the binary libtermcap.a, it is unlikely that the library still prints
 
 =2E..or, I assume in libtermcap.so
 
 Did anyone run ldd on the xterm to see if it's statically linked against
 libtermcap.*, or dynamically?  If the former, you could do a strings on
 the executable (though I don't know why one would use static linking in
 this case).
 
 However - the report points to the applications running in xterm (aside
 from the puzzling comment about the X resources).  Those can also be
 inspected for their use of libtermcap.*
 
 > "OOPS".  Are you sure you tried -current?  Or you could just apply the
 > patch to whatever sources you use:
 >=20
 >    cvs diff -r 1.23 -r 1.25 src/lib/term/t_goto.c
 >=20
 > Is it possible that your xterm is linked against a non-NetBSD libtermcap?
 
 hmm "your" appears in an odd context.  It wasn't my bug report, but I
 maintain xterm.
 
 However - xterm will link against anything that claims to be termcap,
 but its configure script checks for "real" termcap versus terminfo.
 So it would be possible to have these cases:
 
 	a) normal (link against system's termcap library)
 
 	b) broken (system's termcap is missing, and the configure script
 	   finds some other flavor of termcap).  A broken case can be
 	   constructed by using explicit -L options to force the program
 	   to link against some other flavor - but then that's a problem
 	   with the build system (you have to work to make it do the
 	   wrong thing).
 
 --=20
 Thomas E. Dickey
 http://invisible-island.net
 ftp://invisible-island.net
 
 --liOOAslEiF7prFVr
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (SunOS)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQFFJOO6tIqByHxlDocRAu/cAKCxK9NA4Ebx+yl+v2fAcKMKHql0nQCggYRq
 NTSv+MXRO2fvd1rMhAKMLIA=
 =bjzJ
 -----END PGP SIGNATURE-----
 
 --liOOAslEiF7prFVr--