The ancient version of binutils in the cross-binutils port suffers for
several vulnerabilities. Mark it FORBIDDEN and DEPRECATED and set it expire
April 15th.
This also effects devel/mingw64-binutils.
Consumers of this port should switch to devel/binutil or slave ports
there of.
PR: 198816
Reported by: Sevan Janiyan <venture37@geeklan.co.uk>

devel/cross-binutils: Fix and update to 2.23.2
- For mips no gprof was built, so installing failed.
- Building failed for ppc in version 2.21.
- Add an option for the switch WITH_RTEMS_PATCHES
Christoph has also valiantly agreed to be set as MAINTAINER.
PR: ports/177851
Submitted by: Christoph Mallon <christoph.mallon@gmx.de>

- Return my ports back to the pool. I was unable to make any fixes to
my ports in the past 3 weeks while ports were broken on any 10.x
machines, which means I'm unable to maintain them. So let people know
that there's no available support for them until things are back to
normal (which also means that anyone with spare time will be able
to fix them without getting approval).

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