From owner-freebsd-current@FreeBSD.ORG Wed Aug 4 23:28:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 780DB16A4CE for ; Wed, 4 Aug 2004 23:28:55 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5880E43D41 for ; Wed, 4 Aug 2004 23:28:55 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) i74NStlA009960 for ; Wed, 4 Aug 2004 16:28:55 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)i74NStAw009959 for freebsd-current@freebsd.org; Wed, 4 Aug 2004 16:28:55 -0700 (PDT) (envelope-from sgk) Date: Wed, 4 Aug 2004 16:28:54 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20040804232854.GC9742@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: something strange with amd64 or fetch or ports or gcc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Aug 2004 23:28:55 -0000 While trying to build math/octave, make(1) stopped with lapack.tgz 99% of 4874 kB 2448 kBps fetch: lapack.tgz appears to be truncated: 4991991/4991992 bytes >> Couldn't fetch it - please try to retrieve this >> port manually into /usr/ports/distfiles/lapack and try again. *** Error code 1 Stop in /usr/ports/math/atlas/work/lapack. *** Error code 1 Stop in /usr/ports/math/atlas. I simply restarted make(1) and the port infrastructure computed and validated the md5 checksum on lapack.tgz without me manually retrieving the tar ball. So all 4991992 bytes were successfully retrieved from netlib.org. The system is a SMP amd64 system, and FreeBSD (world and kernel) were rebuild from today's sources. I use the standard CFLAGS of "-O -pipe". I haven't seen other reports of this behaviour. This could be amd64 specific, caused by the new gcc, a 64-bit issue with fetch (I doubt this it, but...), or some problem in the ports system *.mk glue. -- Steve