Update binutils to 2.33.1

While here, convert binutils into flavors, that ease a lot maintenance
and helps cleaning out the code.

This is inspired by the same work on going on the xtoolchained gcc by jhb@

PR:		241756
Exp-run:	antoine (portmgr)
Discussed with:	jhb
Differential Revision:	https://reviews.freebsd.org/D22258

Update binutils to 2.31.1

Commit plist changes forgotten in previous update

Reported by:	antoine, Mark Millard <markmi@dsl-only.net>

Update to 2.27

Remove aarch64 patches which are now upstream
Disable new x86 relocation to avoid incompatibilities with the old base binutils
Activate all targets on the default binutils (requested by royger@)
Add a RELRO option (default off) to be able to define the default behaviour of
ld(1) on passing or not -z relro

Remove the old patch since it has been integrated upstream now.

avr-binutils patch has to be updated for binutils 2.25

Cleanup plist

Restore my maintainership on this port.

Add missing file in pkg-plist.

Reorganize the avr-binutils port to use the central binutils one
(as the various arm*binutils ports are doing, too).

Add a patch to recognize the "avrtiny" architecture MCUs (ATtiny10
et al.), extracted from the Atmel AVR Toolchain 3.4.5 (they still
didn't push it upstream, alas).

Upgrade to version 2.24.

Add staging support.

Submitted by:	pi

Add NO_STAGE all over the place in preparation for the staging support (cat:
devel part 1)

Disable gettext, that fixes a conflicts with devel/binutils

Approved by:	joerg (maintainer)

Fix build disabling -Werror

- Convert USE_GETTEXT to USES (part 3)

Approved by:	portmgr (bapt)

Force numerous ports that fail to build with clang over to instead always
rely on gcc.  The patch uses the new USE_GCC=any code in Mk/bsd.gcc.mk to
accomplish this.

The ports chosen were ports that blocked 2 or more ports from building with
clang.  (There are several hundred other ports that still fail to build with
clang, even with this patch.  This is merely one step along the way.)

Those interested in fixing these ports with clang, and have clang as their
default compiler, can simply set FORCE_BASE_CC_FOR_TESTING=yes.

For those who have gcc as their default compiler, this change is believed
to cause no change.

Hat:		portmgr
Tested with:	multiple runs on amd64-8-exp-bcm and 9-exp-clang, with various
		combinations of patch/no-patch and flag settings.

Fix the plist for this port.

Reminded by:  pav

Upgrade to binutils 2.20.1.

Completely reorganize the patches for this port.

Patches for new devices are now synchronized with the Atmel AVR tools.
The main difference is the naming scheme, as FreeBSD patches start
with "patch-", while the Atmel AVR Tools patches end up in ".patch".

Avoid conflict with devel/binutils when installing info files.

PR:             ports/162248
Submitted by:   4720@hushmail.com

Fix dependency on gettext; runtime needed too

PR:             ports/162117
Submitted by:   4720
Approved by:    joerg via email

- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead

PR:             157936
Submitted by:   myself
Exp-runs by:    pav
Approved by:    pav

- Use canonical format for FreeBSD.org MAINTAINER addresses
- Remove obsolete MD5 checksum while I'm here

PR:             ports/152844
Submitted by:   sunpoet (myself)
Approved by:    miwi (with portmgr hat)

Autotools update.   Read ports/UPDATING 20100915 for details.

Approved by:    portmgr (for Mk/bsd.port.mk part)
Tested by:      Multiple -exp runs

Bounce PORTREVISION for gettext-related ports.  Have fun, ya'll.

This one has to go away.

Feature safe: yes

Oops, forgot to also commit the new distinfo.

Feature safe: yes

Upgrade to GNU binutils 2.20, including patches from WinAVR 20100110.

Feature safe: yes

Upgrade to GNU binutils 2.19.1.

Integrate another bugfix that affects avr25-architecture MCU types
(ATtiny84, for example).

Add some NLS files that slipped through in my previous commit.

Noticed by:     QAT

Upgrade to GNU binutils 2.19 (finally).

Add the missing ATxmega ldscript files to pkg-plist.

Incorporate the ATxmega patch from WinAVR.

Silense an assembler warning that triggered too frequently on
legitimate code (binutils bug 5523).

Make $DATA_ORIGIN a configurable value within the linker script
templates.

Add support for ATtiny88, ATmega32HVB, ATmega1284P.
Fix support for AT90USB82/162, move them into "avr35" architecture.
Add basic support for fuse and lock bit sections in ELF file.

Fix broken package list.

Approved by:    portmgr (erwin)

Update to binutils-2.18.

Add device support for ATmega8HVA/ATmega16HVA.

Change AT90USB82 from avr5 to avr5.

Add AT90PWM1, AT90USB82/162, and ATmega32[59]0?p devices.

Fix a compiler warning in the AVR-COFF generator that appeared with
GCC 4.x, and caused the compilation to fail due to the -Werror option
used.

Remove an annoying assembler warning in the ATmega256x patch that was
frequently triggered by large C switch() statements in GCC, and
generally considered to be a regression.  The author of that patch
agreed that the warning isn't particularly useful anyway for a number
of reasons, and recommended to just drop it.

Try to remove the "rw" locale directories when uninstalling.

Update the description to match the reality:

. we are based on binutils-2.17 now
. most of the AVRs are now supported by the stock distribution of
  binutils now, so update our local additions

Upgrade to binutils 2.17, and add the ATmega256x patch from Björn
Haase.

Rename ATmega164/324 to ATmega164P/324P, add support for ATmega644P,
ATmega165P, and ATmega169P.

Umpf, fix the fix. :-(  We want to support the AT90USB646 (and 647),
not the AT90USB468.

Forgot to commit the patch for AT90USB647.

Add support for the ATmega406 and AT90USB646/647/1286/1287 devices.

Conversion to a single libtool environment.

Approved by:    portmgr (kris)

SHA256ify

Approved by:    krion@

Add support for ATtiny261/461/861.

Add support for ATtiny24/44/84 devices.

Mass-conversion to the USE_AUTOTOOLS New World Order.  The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.

Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.

Preliminary documentation can be found at:
        http://people.FreeBSD.org/~ade/autotools.txt

which is in the process of being SGMLized before introduction into the
Porters Handbook.

Light blue touch-paper.  Run.

Upgrade to binutils 2.16.1.

Add support for AT90CAN32/64.

Document our private extensions in the package description.

Remove individual patches for adding new AVR devices to the toolchain,
and combine them into a single unified patch, as only two files need
to be patched anyway.

This will extend support of avr-binutils (over stock binutils-2.16) to
the following AVR devices:

ATtiny25/45/85
AT90PWM2/3
ATmega164/324/644
ATmega329/3290/649/6490
ATmega640/1280/1281

Bump port revision for the fixed PLIST.

Forgot to fix the plist after the recent upgrade to 2.16.

Update to binutils-2.16.

A number of our old patches have been integrated into the mainline now,
so they can be removed.

I just noticed I forgot to cvs add the ATmega1280 patch last time.

In preparation for moving the port to binutils-2.16, rather get it
in before that.

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'.

Merge some patches that have meanwhile be integrated in binutil's CVS,
and apply them to the latest released version (2.15).  This mainly
adds support for new AVR devices that appeared on the market recently,
and fixes one relocation bug for the EEPROM section that could be
noted when a bootloader section is also present.

Apply a big libtool patch to allow porters to use the libtool installed by
the libtoolX ports instead of the one included with each port.  Ports that
set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of
the included version.  To restore previous behavior, use the new macro,
USE_INC_LIBTOOL_VER.  Both macros accept the same argument: a libtool version.

For example, to use the ports version of libtool-1.5, add the following to
your Makefile:

USE_LIBTOOL_VER=        15

To use the included version of libtool with extra hacks provided by
libtool-1.5, add the following to your Makefile:

USE_INC_LIBTOOL_VER=    15

With this change, ports that had to add additional libtool hacks to prevent
.la files from being installed or to fix certain threading issues can now
delete those hacks (after appropriate testing, of course).

PR:             63944
Based on work by:eik and marcus
Approved by:    ade (autotools maintainer)
Tested by:      kris on pointyhat
Bound to be hidden problems:    You bet

Upgrade to binutils 2.15.

Also fixed is the way the tweak for amd64 -> x86_64 is done, and
Manuel Stuehn <manuel dot stuehn at gmx dot net> verified it is OK
on that architecture now.

When compiling on an amd64 host, override the --host configure setting
to x86_64 to make the GNU utils match their expectation.

Noticed by:     kris

SIZEify (maintainer timeout)

Whoa there, boy, that's a mighty big commit y'all have there...

Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".

For ports-in-waiting:

        USE_LIBTOOL=YES         ->      USE_LIBTOOL_VER=13
        USE_AUTOCONF=YES        ->      USE_AUTOCONF_VER=213
        USE_AUTOMAKE=YES        ->      USE_AUTOMAKE_VER=14

Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.

Bump PORTREVISION on all ports that depend on gettext to aid with upgrading.

(Part 2)

Update to binutils 2.14.

Also included now the "AVR COFF beta" patch that allows avr-objcopy to
generate AVR (extended) COFF files.  Note the beta state (which only
affects this conversion though).

This commit also fixes a minor pkg-plist problem noticed by kris.

Utilize INFO.  The pkg-plist still appears to be broken.

Clear moonlight beckons.
Requiem mors pacem pkg-comment,
And be calm ports tree.

E Nomini Patri, E Fili, E Spiritu Sancti.

Upgrade from our previous snapshot to the official latest release of
binutils, 2.13.2.1.

Mega-upgrade the AVR GNU utils toolchain, part #1:
Upgrade binutils to a recent snapshot, since this is a prerequisite
for the remaining ports.

Unfortunately, sources.redhat.com frequently purges older snapshot
tarballs, thus i gotta keep the one to use here around privately.

USE_LIBTOOL implies GNU_CONFIGURE, so remove the latter where appropriate.    

As a side-effect of no longer installing libbfd, some header files   that used
to be mentioned in the PLIST aren't installed anymore   either.    

Do not, never, nikogda install lib{bfd,opcodes,iberty}.a.  They might   clash
with other binutils ports for different targets, and are not   needed to be
installed at all.    

Don't install libiberty.a, it's not required to be installed, and likely   to
clash with other ports of GNU tools.    

Resurrect obrien's update to binutils 2.11 from the depths of CVS,   now that
I'm ready to upgrade the entire AVR toolchain.    

Back out the 2.10.1 -> 2.11 upgrade.  The avr-gcc port just didn't like it.   I
upgrade this in too much hast for 4.3.    

Use out libtool.    

Update to Binutils 2.11[.0].    

This is the first port of a fairly complete toolchain for Atmel AVR  
microcomputer cross-development.  More (avr-gcc, avr-libc) to follow...