findutils @4.9.0 +universal configure fails on Snow Leopard due to 32-bit time_t warning

[rlhamil]

findutils +universal now may have a problem configuring where that includes 32-bit, specifically seen on Snow Leopard

:info:configure configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_findutils/findutils/work/findutils-4.9.0-i386':
:info:configure configure: error: The 'time_t' type stops working after January 2038,
:info:configure                    and your system appears to support a wider 'time_t'.
:info:configure                    Try configuring with 'CC="/opt/local/bin/clang-mp-8.0 -m64"'.
:info:configure                    To build with a 32-bit time_t anyway (not recommended),
:info:configure                    configure with '--disable-year2038'.

[mascguy (Christopher Nielsen)]

This port was fixed several years ago, to ensure that configure only warns about that. And that's what I'm seeing locally, when testing on 10.5 and 10.6.

Are you using an out-of-date - or custom - portfile?

[mascguy (Christopher Nielsen)]

Replying to mascguy:

This port was fixed several years ago, to ensure that configure only warns about that. And that's what I'm seeing locally, when testing on 10.5 and 10.6.

Are you using an out-of-date - or custom - portfile?

Regardless, I'll add configure option --disable-year2038, to eliminate the warning entirely.

[rlhamil]

As of when I filed it was current (as in port selfupdate or port sync) and not custom and no Portfile in the current directory then, and nothing strange on the port upgrade command line either.

[Christopher Nielsen <mascguy@…>]

In 68bc72812c334a2f5a33f96c28e5ae1874d8afae/macports-ports (master):

findutils-devel: i386/ppc: disable year 2038 support
See: #65458

[Christopher Nielsen <mascguy@…>]

In a0d28128159032f5e8d61c43b120b627cf78eab4/macports-ports (master):

findutils: i386/ppc: disable year 2038 support
Fixes: #65458

[jmroot (Joshua Root)]

Replying to mascguy:

This port was fixed several years ago, to ensure that configure only warns about that. And that's what I'm seeing locally, when testing on 10.5 and 10.6.

Were you building on 64-bit hardware? I gather that it only complains if you are building 32-bit on a system that can build 64-bit.

[rlhamil]

Replying to jmroot:

Replying to mascguy:

This port was fixed several years ago, to ensure that configure only warns about that. And that's what I'm seeing locally, when testing on 10.5 and 10.6.

Were you building on 64-bit hardware? I gather that it only complains if you are building 32-bit on a system that can build 64-bit.

Building on a Snow Leopard VM on a 64-bit Mojave host; so yes, I expect the VM was 64-bit capable. There were some thing I built universal "just in case", although I grant that findutils (since it doesn't apparently provide library/libraries) is not a particularly good example of that argument.