From owner-freebsd-stable  Sat Oct 28 12:43:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mumble.foobie.net (adsl-216-103-105-178.dsl.snfc21.pacbell.net [216.103.105.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1223B37B479; Sat, 28 Oct 2000 12:43:32 -0700 (PDT)
Received: (from sbeitzel@localhost)
	by mumble.foobie.net (8.11.0/8.11.0) id e9SJhVH28741;
	Sat, 28 Oct 2000 12:43:31 -0700 (PDT)
	(envelope-from sbeitzel)
From: Stephen Beitzel <sbeitzel@mumble.foobie.net>
Message-Id: <200010281943.e9SJhVH28741@mumble.foobie.net>
Subject: Re: hang when making port
To: patrick@FreeBSD.ORG (Patrick Gardella)
Date: Sat, 28 Oct 2000 12:43:31 -0700 (PDT)
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <39FB22B1.460BA9A0@freebsd.org> from "Patrick Gardella" at Oct 28, 2000 03:02:09 PM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Patrick Gardella <patrick@freebsd.org> wrote:
> 
> It's not specifically related, since I have a system that was created
> after the entire ports tree was updated, and am having the problem as
> well.  
> 
> And it only hangs after the last item is fetched, it looks like its
> before or during the checksum.

I've noticed what I believe may be the same problem, but it's only
happening with some ports. Yesterday (10/27/2000) I cvsupped a fresh ports
tree and then tried making XFree86, but both 3.x and 4.x hung just after
fetching the tarballs. Meanwhile, making w3m-ssl works just fine. So I
suspect that the problem is not a general "all ports are broken" but
a more specific one, like "some ports are broken at the point where they
check the MD5 of the tarball".

Just another data point.

Steve


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message