From owner-freebsd-ports@FreeBSD.ORG  Thu Aug 26 11:53:43 2010
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6784510656A4;
	Thu, 26 Aug 2010 11:53:43 +0000 (UTC) (envelope-from stb@lassitu.de)
Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea])
	by mx1.freebsd.org (Postfix) with ESMTP id 30A888FC1D;
	Thu, 26 Aug 2010 11:53:43 +0000 (UTC)
Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id DDB57DBAE;
	Thu, 26 Aug 2010 11:53:41 +0000 (UTC)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Stefan Bethke <stb@lassitu.de>
In-Reply-To: <201008052132.o75LWtO6010244@localhost.cwsent.com>
Date: Thu, 26 Aug 2010 13:53:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <11FF87D7-FF70-4ABC-8A5B-39307BC78C5F@lassitu.de>
References: <201008052132.o75LWtO6010244@localhost.cwsent.com>
To: cy@freebsd.org
X-Mailer: Apple Mail (2.1081)
Cc: freebsd-ports@freebsd.org
Subject: Re: sysutils/screen fails to build 
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2010 11:53:43 -0000

Am 05.08.2010 um 23:32 schrieb Cy Schubert:

> I'm in Newfoundland at the moment and will return home on Aug 17. I'll
> look at this when I return.

I finally got around figuring out why the screen update was failing on =
just this one box, while all my other -stables are just fine.  The =
problem was an accidental upgrade to -current on that box, followed by a =
downgrade to -stable, back in May.  Apparently, some -current includes =
and libraries are still hanging around, and are picked up by configure, =
specifically libulog and libutempter, but they are referencing symbols =
not available in the -stable libs.


Sorry to bother you,
Stefan

--=20
Stefan Bethke <stb@lassitu.de>   Fon +49 151 14070811