Back to the Future - 64-bit time_t on sparc64
Garance A Drosihn
drosih at rpi.edu
Tue Feb 17 12:05:21 PST 2004
At 10:06 PM -0600 2/16/04, Tillman Hodgson wrote:
>On Mon, Feb 16, 2004, Garance A Drosihn wrote:
>> This is described in a little detail in the UPDATING.64BTT file.
>Speaking of which, in that document you mention the problem with
>portupgrade and note that you have a prebuilt package available
The issue is 'cvsup', not portupgrade. My point was that you
should not run 'cvsup' before trying to recompile ports. That
is partially because the cvsup you *have* (which would be a
32-bTT version of cvsup) will not work until you recompile
it -- so of course you can't run it before recompiling your
Perhaps I need to come up with better wording for that section.
Also note that if you *do* recompile all of ezm3 and cvsup,
then you will have a 64-bTT version, and that will work okay.
>Is that necessary, or will a portupgrade of portupgrade itself
>generally compile fine (allowing one to use the newly compiled
>version of portupgrade to get the rest of the ports done)?
As noted in the writeup, start out with
portupgrade -Rr -f portupgrade ruby
and everything should work out okay.
Garance Alistair Drosehn = gad at gilead.netel.rpi.edu
Senior Systems Programmer or gad at freebsd.org
Rensselaer Polytechnic Institute or drosih at rpi.edu
More information about the freebsd-sparc64