Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Nov 2002 17:40:47 -0800
From:      Peter Wemm <peter@wemm.org>
To:        ia64@freebsd.org
Subject:   Warning: time_t
Message-ID:  <20021116014047.E40AC2A88D@canning.wemm.org>

next in thread | raw e-mail | index | archive | help
I suspect that all 3 FreeBSD/ia64 users know about this already, but just in
case there are some stealth users that I dont know about, beware of the 64
bit time_t in -current.

In all, it should be pretty transparent.  I recently upgraded a 6-month-old
ia64 world to -current and did the time_t jump at the same time, and all
things considered, it went pretty well.  What ended up killing me was
that I prematurely installed new /usr/include, without the corresponding
libc.so.5 changes.  Aside from that silly mistake (which broke install(8)
when it used utime(3)), it goes fairly well.

Expect 3 alignment fixes during 'installworld'.  This is because
the *old* dynamic /tmp/install.XXXXX/find is being run with the new
/usr/lib/libc.so.5.  'make installworld' doesn't fail for me though.
But to be safe, run a second 'installworld' to be sure.

Aside from that, it should be pretty uneventful.  Now to find out why
sshd blows up with PrivSep turned on.

Cheers,
-Peter
--
Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021116014047.E40AC2A88D>