devel/avr-gcc: Upgrade to 14.1.0

This upgrades AVR-GCC to GCC 14.1.0

One patch has been added that fixes GCC PR ipa/92606. This will
become obsoleted when GCC 14.2 is out.

devel/avr-gcc: Moved man to share/man

Approved by:    portmgr (blanket)

devel/avr-gcc: Fix build with libc++ 17

gcc/system.h includes safe-ctype.h which redefines ctype macros such
as toupper, tolower, etc to "poison" them.

However, it should only include the safe-ctype.h header *after* any
C++ headers, such as <list>, <map>, <string>, etc, otherwise these
might transitively include internal ctype headers (such as with libc++
17), causing compilation errors.

PR:		274038
Reported by:	dim

*: Bump PORTREVISIONs for math/mpc update to 1.3.1

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

devel/avr-gcc: Update to GCC 11.2

Also include the specs file for recent AVR-Dx MCUs (e.g. AVR128DA48
etc.), so the compiler can handle these, in addition to the builtin
MCU types. These files come straight from the Microchip device pack.

devel/avr-gcc: upgrade to GCC 10.3.0

devel/avr-gcc: Add CPE information

Approved by:	portmgr (blanket)

Update to GCC 10.2.0
PR:		255454
Differential Revision:	https://reviews.freebsd.org/D30022

devel/avr-gcc: Put variables in order and format Makefile

Approved by:	portmgr blanket

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

Update to MPC version 1.2.0 with the following changes:
 - New functions:
   . mpc_sum
   . mpc_dot
 - Several functions are more robust with a reduced exponent range
   (for example corresponding to IEEE 754 binary formats).
 - New mpcheck tool for comparison with the native C library (which
   is not installed by default).

Bump all directly dependent ports. Do not bump those indirectly
dependent via the lang/gcc* family since their run-time dependencies
and code generated should not be affected.

PR:		249950
Submitted by:	wen

devel/avr-gcc: fix build on powerpc64le

Merge upstream GCC patch to fix build on powerpc64le.

devel/isl: Update to 0.23

PR:		251432

These ports now build on aarch64.

Approved by:	portmgr (tier-2 blanket)
Obtained from:	lonesome.com TRYBROKEN run

add objdump binutils dependencies to remaining devel/* ports

/usr/bin/objdump has been removed from the base system before FreeBSD 13.0.

Approved by:	bapt (implicit)

devel/avr-gcc: fix build on powerpc64 elfv2

This port needs a patch similar to other GCC ports to avoid namespace collision
on powerpc64 elfv2.

PR:		242284
Approved by:	joerg (maintainer timeout)

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

devel/avr-gcc: fix build on GCC architectures

GCC 9.1 needs newer GCC to build than base can offer.

It also seems that there are some threading issues, so put MAKE_JOBS_UNSAFE.

PR:		240002
Approved by:	joerg (maintainer), linimon (mentor)

Update to GCC 9.1.0

PR:		239628
Submitted by:	Oleg Sidorkin

Add explicit USES=iconv

Reported by:	pkg-fallout (via devel/avr-libc)

Install texinfo files (GNU info) into ${PREFIX}/share/info

After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.

Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.

Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them

Bump revision of all impacted ports

PR:		232907
exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D17816

Add missing USES=makeinfo

devel/avr-gcc: fix build with recent clang

PR:		227650
Submitted by:	dim@
Reported by:	 Kenji Rikitake
Approved by:	maintainer-timeout
MFH:		2018Q3

Update mpfr to 4.0.1 release and bump PORTVERSION of dependent ports.

Bump PORTREVISIONs of all users of math/mpc that we just updated to
version 1.1.0 (via revision 464079).

Make defining both PORTVERSION and DISTVERSION a DEV_ERROR.

There are two cases:

- The upstream versionning is compatible with our versionning, or using
  DISTVERSION's magic leads to a compatible PORTVERSION, use
  DISTVERSION.  If it is possible to use DISTVERSIONPREFIX and
  DISTVERSIONSUFFIX to make it compatible, use them.
- The upstream versionning is not compatible with our versionning, and
  DISTVERSION's magic does not lead to a correct PORTVERSION, then set
  PORTVERSION to the equivalent of our versionning, and set DISTNAME.
  It is possible to use a third variable where you store upstream's
  version and use it to compute PORTVERSION and/or DISTNAME, like the
  dns/bind9* ports do.

Sponsored by:	Absolight

Apply r432958 from lang/gcc5 to devel/avr-gcc to fix build with recent
versions of libc++

Reported by:	pkg-fallout

Upgrade to GCC 5.4.0.

Mark various ports broken on aarch64 and armv6.

Approved by:	portmgr (tier-2 blanket)

Do not use post-stage.  Use post-install instead.

The only reason to use post-stage is because the port needs to do
"things" at a later time, like some plist manipulation.
While there, fold post-install in do-install targets when they are
defined.

PR:		214780
Submitted by:	mat
Exp-run by:	antoine
Sponsored by:	Absolight

Fix build with libc++ 3.9.0

PR:		212696
Submitted by:	dim
Approved by:	maintainer timeout (1 month)

Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.

With hat:	portmgr
Sponsored by:	Absolight

Upgrade to GCC 4.9.3.  (5.3 not yet there, still doing some tests,
4.9.x is quite stable.)

- Make NLS optional

PR:		203622
Submitted by:	amdmi3
Approved by:	maintainer timeout (joerg, 1 month)

MASTER_SITES cleanup.

- Replace ${MASTER_SITE_FOO} with FOO.
- Merge MASTER_SITE_SUBDIR into MASTER_SITES when possible. (This means 99.9%
  of the time.)
- Remove occurrences of MASTER_SITE_LOCAL when no subdirectory was present and
  no hint of what it should be was present.
- Fix some logic.
- And generally, make things more simple and easy to understand.

While there, add magic values to the FESTIVAL, GENTOO, GIMP, GNUPG, QT and
SAMBA macros.

Also, replace some EXTRACT_SUFX occurences with USES=tar:*.

Checked by:	make fetch-urlall-list
With hat:	portmgr
Sponsored by:	Absolight

Cleanup plist

Remove some overusage of PERL_ARCH.

Sponsored by:	Absolight

Add a patch for ATmega*RFR*, as has already been promised in the
pkg-descr file.

Fix plist

Update pkg-plist (forgotten in previous commit).

Add staging support.

Upgrade to a recent GCC version (4.8.3).

Drop most of our local hacks.

PR:		192399
Submitted by:	pi

Convert a bunch of USE_BZIP2 to USES=tar:bzip2

Approved by:	portmgr (not really, but touches unstaged ports)

Actually, the configure error is during the build phase

With hat:	portmgr

Mark BROKEN: Fails to configure with avr-binutils 2.24

checking for suffix of object files... configure: error: in
`/wrkdirs/usr/ports/devel/avr-gcc/work/build/avr/avrtiny10/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
gmake[1]: *** [configure-target-libgcc] Error 1

Reported by:	pkg-fallout
With hat:	portmgr

Resetting maintainership on ports that have not been staged and without any
pending PR (related to stage)

With hat:	portmgr

Update to libmpc version 1.0.1 which brings the following fixes:

 - Switched to automake 1.11.6, see CVE-2012-3386.
 - #14669: Fixed extraction of CC from gmp.h.
 - Fixed case of intermediate zero real or imaginary part in mpc_fma,
   found by hydra with GMP_CHECK_RANDOMIZE=1346362345.

This is on top of the following changes from version 1.0

 - Licence change towards LGPLv3+ for the code and GFDLv1.3+ (with no
   invariant sections) for the documentation.
 - 100% of all lines are covered by tests
 - Renamed functions
   . mpc_mul_2exp to mpc_mul_2ui
   . mpc_div_2exp to mpc_div_2ui

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

- convert to the new perl5 framework
- convert USE_GMAKE to Uses

Approved by:	portmgr (bapt@, blanket)

Attempt to fix building on recent head

- Convert USE_GETTEXT to USES (part 4)

Approved by:	portmgr (bapt)

Fix build with clang

PR:		ports/176961
Submitted by:	myself
Approved by:	maintainer timeout

Convert USE_BISON to USES= bison

It brings bison as a build dependency in case it is set the following way:
USES= bison or USES= bison:build

it brings bison as a run dependency in case it is set the following way:
USES= bison:run

it brings bison both as a run and build dependency in case it the set the
following way:
USES= bison:both

While here trim some headers
Convert some USE_GNOME= gnomehack to USES= pathfix

Unbreak devel/avr-gcc:

. fix pkg-plist
. mention gettext prerequisite
. use the correct objdump utility

PR:             ports/164874
Submitted by:   Michael Scheidell
Approved by:    portmgr (erwin)
Feature safe:   yes

- Mark BROKEN (at least) on amd64: does not package

Reported by:    pointyhat

Upgrade to GCC 4.5.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".

- 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)

Chase mpfr library and bump PORTREVISION.

Switch to use newer GMP version.

PR:             ports/144487
Submitted by:   ale
Approved by:    portmgr (-exp run by erwin)

Upgrade to GCC 4.3.4, as well as to the patches from WinAVR 20100110

Yet another forgotten line, sigh.

Add two entries I forgot previously.

Update the Xmega patch.  Among adding support for some newer
Xmega MCU types, this adds an important bugfix for printf & Co.
functions.

Use the undocumented feature WITHOUT_CPU_CFLAGS rather than MAKE_ENV
to avoid application of the host's CPU architecture options to the
cross-compilation environment.

Found by:       Dominic Fandrey

Update to GCC 4.3.2.

(The old port will be migrated to devel/avr-gcc-42 within the next
days.)

Add plist files forgotten in last update.

Reminded by:    pav

Add support for ATtiny88, ATmega32HVB, ATmega1284P.
Fix support for AT90USB82/162, move them into "avr35" architecture.
Add support for the OS_main and OS_task attributes.

Integrate some more bugfixes from the WinAVR patch list.

Upgrade to GCC 4.2.2

Migration from bison 1.x to 2.x

PR:             117086
Tested by:      -exp runs

Welcome bsd.perl.mk.  Add support for constructs such as USE_PERL5=5.8.0+.
Drop support for antique perl.

Work done by:   gabor
Sponsored by:   Google Summer of Code 2007
Hat:            portmgr

Add device support for ATmega8HVA/ATmega16HVA.

Change AT90USB82 from avr5 to avr5.

Add the Russian message catalog file to pkg-plist.

Minor fix for AT90USB* devices.

Submitted by:   Anatoly Sokolov

Also spell-fix `PORTREVISION' *blush*.

Fix pkg-plist after version upgrade.

Reminded by: pointyhat.

Upgrade to GCC 4.1.2.

Add support for AT90PWM1, ATmega32[59]0?P, AT90USB82/162.

OK, I bite.  Implement the patch from PR ports/96407, to avoid the
-mcpu=foobar braindeadness.

There's a GCC bug open for this:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25672
so at least, the issue is being dealt with in its origin.

Submitted by:   Alex Mogilnikov <alx@intellectronika.ru>
PR:             ports/96407

Change private hack into @dirrmtry.

Copy over the avr-gcc-devel port to avr-gcc, so this will become the
default AVR-GCC version now.

No repocopy as this port used to exist before.  For the history details,
see the old avr-gcc-devel port (going to be moved to Attic now).

devel/avr-gcc has been repocopied to devel/avr-gcc-3, so to make room
for devel/avr-gcc-devel taking over the role of the default AVR-GCC
port now.

Fix the link specification in the patch so ATmega*P devices will get
their correct -Tdata option passed down.

Submitted by:   Anatoly Sokolov

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

Upgrade to GCC 3.4.6.
Add support for ATmega406 and AT90USB646/647/1286/1286 devices.
Register conflict for avr-gcc-devel port (GCC 4.1-based, to come soon).

Fix the severe bug (faulty code generation) reported in

<http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26118>

by reverting the GCC change that obviously caused it.

Approved by:    portmgr (krion)

SHA256ify

Approved by:    krion@

Add support for ATtiny261/461/861.

Upgrade to GCC 3.4.5, and 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.

Add support for the AT90CAN32/64 controllers.

By the same time, also drag in the patch for catching
misspelled interrupt vector names from the 4.x branch of
GCC.

Add support for the ATmega640/1280/1281 family.

Oops, a double slash sneaked into the linker spec, causing GCC to
recurse infinitely, until it hit an abort().

Add back support for the ATmega165.

Fix the linker command (in GCC's specs file) for the AT90PWM2/3
controllers.

Approved by:    portmgr (linimon)

Remove a superfluous part of a patch (patching a .orig file resulting from
a previous patch).

No PORTREVISION bump as the resulting binaries are identical.

Upgrade AVR-GCC to GCC-3.4.4.

By the same time, combine all the patches that add support for new AVR
devices into a single patch, as they all touch the same three source
files.  In total, add support for the following AVR devices that were
not supported by the stock GCC 3.4.x:

  ATtiny13/ATtiny2313
  ATtiny25/ATtiny45/ATtiny85
  ATmega48/ATmega88/ATmega168
  AT90PWM2/AT90PWM3
  ATmega164/ATmega324/ATmega644
  ATmega325/ATmega3250/ATmega645/ATmega6450
  ATmega329/ATmega3290/ATmega649/ATmega6490
  AT90CAN128

(This is now documented in pkg-descr as well.)

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

Bring in some patches from the head of GCC's CVS back to the latest
released version, 3.4.3.  This mainly adds support for new AVR devices
that appeared on the market recently, and fixes a bug related to the
order of assignments for volatile uint16_t * objects (in the
assumption they might point to IO space where the order of two 8-bit
operations can be important).

Do also set IGNORE when running against a too old version of Perl
where we can't build the docs.

Hinted by:      kris