ports/66159: [PATCH] Fix ezm3 for 64-bit time_t on sparc64 5.x-current

[Garance A Drosehn]

>Number:         66159
>Category:       ports
>Synopsis:       [PATCH] Fix ezm3 for 64-bit time_t on sparc64  5.x-current
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 01 20:10:21 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Garance A Drosehn
>Release:        FreeBSD 5.2-CURRENT i386
>Organization:
RPI; Troy, NY 
>Environment:
System: FreeBSD freefour.acs.rpi.edu 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Fri Mar 26 15:41:46 EST 2004 root at santropez.netel.rpi.edu:/usr/obj/usr/src/sys/Dual-Athlon2k i386


	Ignore the system-info above.  This is an issue for anyone who wants
	to use cvsup when running on 5.x-current on sparc64 hardware.
>Description:
	The freebsd/sparc64 platform recently switched to 64-bit time_t's.
	ezm3, as it stands, does not handle this.  This is bad for cvsup.
	Right now people using 64-bit time_t's are running a special
	ezm3 package that I have at http://people.freebsd.org/~gad :
		ezm3-64btt-1.1_1.tbz
	along with a special package of cvsup-without-gui as built by
	that version of ezm3, at:
		cvsup-without-gui-64btt-16.1h.tbz
	However, if they rebuild ezm3 from the present ports collection
	then they will run into problems with cvsup.

>How-To-Repeat:
	This has been discussed on freebsd-sparc64 maling list.

>Fix:
	I have a patch at:

	http://people.freebsd.org/~gad/time-64/port-ezm3.diff

	which, if applied to the port, will fix exm3.  There is some
	debate as to whether this is the perfect fix, but it is at
	least a very workable and reliable way to solve the issue.

	One way or another, this issue with the ezm3 port should be
	addressed before we get to 5.3-release.

>Release-Note:
>Audit-Trail:
>Unformatted: