Gearing up for 64-bit time_t on sparc64

David O'Brien obrien at
Wed Jan 7 09:45:33 PST 2004

On Wed, Jan 07, 2004 at 12:08:13AM -0500, Garance A Drosihn wrote:
> How flexible should we be?  My first thought is to tell people:
>    1) upgrade to RELENG_5_2
>    2) *after* you know that upgrade worked, then run a patch
>       file (which will already be in /usr/src?), which will
>       modify the appropriate files needed for this change.
>    3) rebuild after making just that one change.  No cvsup.

I think it has to all be doable given a CVS archive, no external patches.
If need be:

    cvs up -Pd -r RELENG_5_2
    make buildworld
    make kernel
    make installworld

    cvs up -Pd -D '<some date>'
    make ...    ---\
    reboot          | what ever is the debugged order to do things...
    make ...    ---/

    cvs up -PdA
    make buildworld
    make kernel
    make installworld

> Or we could do a more flexible version, combining a -Define in
> CFLAGS (set in /etc/make.conf), along with some extra magic
> when installing the include files during 'make installworld'.
> Some flag such as -DSPARC_TIME_T=BIT32 vs =BIT64.

I think we should only do this if we can't achieve this as above.
> The remaining steps would be the same, but users could flip
> the switch at whatever time they wanted, instead of being
> forced to upgrade to RELENG_5_2.

I think that will be a nightmare of too much potential for people doing
it wrong.

More information about the freebsd-sparc64 mailing list