Date: Tue, 17 Feb 2004 15:05:18 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Tillman Hodgson <tillman@seekingfire.com>, sparc64@freebsd.org Subject: Re: Back to the Future - 64-bit time_t on sparc64 Message-ID: <p0602042ebc5822853d0e@[128.113.24.47]> In-Reply-To: <20040217040616.GL12181@seekingfire.com> References: <p06020407bc533f0ae9d2@[128.113.24.47]> <40306CE7.6080104@mindspring.com> <20040216193108.GE12181@seekingfire.com> <p0602041ebc56dd660908@[128.113.24.47]> <20040217040616.GL12181@seekingfire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
>for download.
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
ports....
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@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0602042ebc5822853d0e>