From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 6 10:00:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45FAB16A4CE; Fri, 6 Feb 2004 10:00:12 -0800 (PST) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A49D43D48; Fri, 6 Feb 2004 10:00:07 -0800 (PST) (envelope-from mi+mx@aldan.algebra.com) Received: from 250-217.customer.cloud9.net (195-11.customer.cloud9.net [168.100.195.11])i16I04aT081858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 6 Feb 2004 13:00:05 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (mteterin@localhost [127.0.0.1]) i16Hxlw3098424; Fri, 6 Feb 2004 12:59:48 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) From: mi+mx@aldan.algebra.com Organization: Murex N.A. To: Adriaan de Groot Date: Fri, 6 Feb 2004 12:59:47 -0500 User-Agent: KMail/1.5.4 References: <200402061837.19872.adridg@cs.kun.nl> In-Reply-To: <200402061837.19872.adridg@cs.kun.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402061259.47401@misha-mx.virtual-estates.net> X-Scanned-By: MIMEDefang 2.39 cc: kde@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] hdf on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 18:00:12 -0000 [CC to the amd64 list because it's particular to that platform; CC to KDE because it's a dependency for their ports, which prevents the ports from building on amd64.] =The attached patch adds support for the amd64 platform by introducing a =new machine definition. I hope I got it all right - in particular, the =code assumes that a fortran int can be cast to a pointer, so I _must_ =define the fortran int as long. I haven't checked if that is really the =case, so while the port may build now, it might not actually work. Thanks for the patch, but I wonder, how this port ever worked for our other 64 bit platforms -- Sparc64 and Alpha. Or is int a 64-bit on those, but not on AMD64? That being said, I was going to ask for retiring the graphics/hdf and repo-copying graphics/hdf5 over it. You may wish to check, if that port has the same problem on AMD64. Yours, -mi