From owner-freebsd-ports@FreeBSD.ORG Mon Jul 3 01:47:46 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FE5C16A412 for ; Mon, 3 Jul 2006 01:47:46 +0000 (UTC) (envelope-from gcr+freebsd-ports@tharned.org) Received: from nc8000.tharned.org (rrcs-24-56-87-26.ma.biz.rr.com [24.56.87.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id D937243D53 for ; Mon, 3 Jul 2006 01:47:45 +0000 (GMT) (envelope-from gcr+freebsd-ports@tharned.org) Received: from nc8000.tharned.org (gcr@localhost [127.0.0.1]) by nc8000.tharned.org (8.13.6/8.13.6) with ESMTP id k631lf5n034821; Sun, 2 Jul 2006 20:47:41 -0500 (CDT) (envelope-from gcr+freebsd-ports@tharned.org) Received: from localhost (gcr@localhost) by nc8000.tharned.org (8.13.6/8.13.6/Submit) with ESMTP id k631leAC034818; Sun, 2 Jul 2006 20:47:41 -0500 (CDT) (envelope-from gcr+freebsd-ports@tharned.org) Date: Sun, 2 Jul 2006 20:47:40 -0500 (CDT) From: Greg Rivers Sender: gcr@tharned.org To: Kevin Oberman In-Reply-To: <20060703003523.B953E45047@ptavv.es.net> Message-ID: <20060702203914.G2155@nc8000.tharned.org> References: <20060703003523.B953E45047@ptavv.es.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: ports@freebsd.org Subject: Re: tcl84 port upgrade fails in test X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 01:47:46 -0000 On Sun, 2 Jul 2006, Kevin Oberman wrote: > I have been unable to update tcl8.4 on my laptop running -current. I > have one other system running -current, but it installed the upgrade > correctly. It compiles without error, but if fails in the tests. > > All of the errors were socket connection failure and included http, > httpold, io, and socket. he test seemed to hang after socket 7.4. > > The network is operating fine on this system, so I have no idea what the > problem might be. > > Has anyone else seen this? > Yes, on a number of machines running -STABLE. I've gotten the port to finish installing by sending SIGTERM to each test process that blocks. You'll get an error like "Test file error: child killed: software termination signal", but it goes ahead and installs. -- Greg Rivers