Number of commits found: 8

Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.

To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.

To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.

Changes to Mk/*:
 - Add runtime detection magic in bsd.port.mk

(Only the first 15 lines of the commit message are shown above )

Reset inactive maintainer who has not responded to email.

Hat:            portmgr

remove USE_REINPLACE for all ports with categories starting with C

Chase shlib bump of libexpat.

Update to 1.2.0

PR:             86562
Submitted by:   maintainer

Chase IETF draft version while i'm here

At Kris's request, back out the MACHINE_ARCH spelling correction until
after 5.4-RELEASE.

Assist getting more ports working on AMD64 by obeying the
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.

o Bump $LIB_DEPENDS line to chase expat's shlib version.
o Bump $PORTREVISION.

Number of commits found: 8

9 vulnerabilities affecting 12 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities