From owner-freebsd-sparc64@FreeBSD.ORG Mon Oct 13 06:42:02 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6227816A4B3; Mon, 13 Oct 2003 06:42:02 -0700 (PDT) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6ACE43FBF; Mon, 13 Oct 2003 06:42:00 -0700 (PDT) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])h9DDfx326736; Mon, 13 Oct 2003 15:41:59 +0200 (MEST) Date: Mon, 13 Oct 2003 15:41:59 +0200 (CEST) From: Harti Brandt To: standards@freebsd.org, sparc64@freebsd.org Message-ID: <20031013153219.H45269@beagle.fokus.fraunhofer.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: time_t on sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2003 13:42:02 -0000 Hi all, I just discovered that time_t is 32-bit on sparc64. One of the problems is that struct timeval is defined by Posix as struct timeval { time_t tv_secs; suseconds_t tv_usecs; }; but _timeval.h has struct timeval { long tv_secs; suseconds_t tv_usecs; } This means, that our timeval is not Posix compatible. What is the reason for time_t not beeing a long on sparc64? harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org