Update to the 20141119 snapshot of GCC 4.9.3.

Update to the 20141105 snapshot of GCC 4.9.3, pretty shortly after
the GCC 4.9.2 release.

Update to the 20141029 snapshot of GCC 4.9.2.

Sort an entry in pkg-plist to be in line with other lang/gcc ports.

Update to the 20141022 snapshot of GCC 4.9.2.

Also remove those traces of @dirrm that were are added dynamically
via the Makefile.

Update to the 20141015 snapshot of GCC 4.9.2.

Update to the 20141008 snapshot of GCC 4.9.2.

Restore the pkg-plist hack to not warn about info/gcc49/dir.

Update to the 20141001 snapshot of GCC 4.9.2.

Comment out info/dir files
indexinfo is taking care of generating it at package installation time

Reported by:	peter

Update to the 20140924 snapshot of GCC 4.9.2.

Remove all instances of @dirrm from pkg-plist.

Update to the 20140917 snapshot of GCC 4.9.2.

Update to the 20140910 snapshot of GCC 4.9.2.

Add USES=libtool

Update to the 20140903 snapshot of GCC 4.9.

Update to the 20140827 snapshot of GCC 4.9.2.

Update to the 20140820 snapshot of GCC 4.9.2.

Update to the 20140813 snapshot of GCC 4.9.2.

Update to the 20140806 snapshot of GCC 4.9.2.

Update to the 20140730 snapshot of GCC 4.9.2.

Update to the 20140723 snapshot of GCC 4.9.2.

Update to the 20140716 snapshot of GCC 4.9.2 which is pretty close to
the upstream GCC 4.9.1 release.

Update to the 20140709 snapshot of GCC 4.9.1.

Also clean *.la files in LIBEXEC, and recursively so, here and for
TARGLIB.

Update to the 20140702 snapshot of GCC 4.9.1.

Update to the 20140625 snapshot of GCC 4.9.1.

Fix build on system built WITHOUT_INFO

With hat:	portmgr

Convert GMAKE to MAKE_CMD
Please note that lots of invocation of MAKE_CMD here are wrong as they do not
properly respect MAKE_ENV and friends

With hat:	portmgr

Update to the 20140618 snapshot of GCC 4.9.1.

Update to the 20140611 snapshot of GCC 4.9.1.

Update to the 20140604 snapshot of GCC 4.9.1.

Update to the 20140528 snapshot of GCC 4.9.1.

Update to the 20140514 snapshot of GCC 4.9.1.

Update to the 20140507 snapshot of GCC 4.9.1.

Convert all :U to :tu and :L to :tl

Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)

bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore

Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier

With hat:	portmgr

Update to the 20140430 snapshot of GCC 4.9.1.

Update to the 20140423 snapshot of GCC 4.9.1.  This is basically the
GCC 4.9.0 release, but since we did not yet use the new way of labeling
snapshots as part of PORTVERSION we could not update to that directly
without using PORTEPOCH.  Going forward that will be possible.

Adjust DISTVERSION and GCC_VERSION to the new PORTVERSION scheme.

Update to the 20140416 snapshot of GCC 4.9.0 which coincides with
RC1 of that release.

Extend full-regression-test by running contrib/test_summary.

Add USES=fortran as another case where the run-time library path is
set transparently.

Reported by:	Dmitry Sivachenko <trtrmitya@gmail.com>

Update to the 20140406 snapshot of GCC 4.9.0.

Add pkg-message that references the need to use -Wl,-rpath=... . [1]

No longer install rebuild-gcj-db49 (which requires bash among others)
and its man page.

PR:		185902 [1]

Update to the 20140330 snapshot of GCC 4.9.0.

Update to the 20140323 snapshot of GCC 4.9.0.

Address a bug where -Wcast-qual would report an incorrect message. [1]

PR:		179204 [1]

Update to the 20140316 snapshot of GCC 4.9.0.

Convert USE_BZIP2 to USES=tar:bzip2.

Update to the 20140309 snapshot of GCC 4.9.0.

This brings back bootstrap-lean which has been fixed upstream last
week, thus consuming less disk space when building this port.

Update to the 20140302 snapshot of GCC 4.9.0.

Forced commit to note that the previous commit (revision 346580) also
included an update of lang/gcc49 to the 20140223 snapshot of GCC 4.9.0.

Remove lang/gcc44 aka GCC 4.4 which has been deprecated since 2011-05-08
and was originally created 2008-03-01, thirteen months before the upstream
release of GCC 4.4.0.  Even lang/gcc45 has been gone for more than two
years now.

Recommend the generic lang/gcc as a replacement.

Set the license to a combination of GPLv3 (for the compiler itself) and
GPLv3 with GCC Runtime Library Exception (for the runtime).

Suggested by:	marino

Update to the 20140216 snapshot of GCC 4.9.0.  Many bugfixes.

Really commit

  No longer run ccache-update-links as part of post-install which, in
  the world of staging, no longer is what it used to be.  Rely on the
  existing @exec and @unexec in pkg-plist instead. [3]

which should have been in the last revision.

Update to the 20140209 snapshot of GCC 4.9.0.

Configure with --enable-gnu-indirect-function to enable the "ifunc"
attribute, a GCC extension. [1]

Remove the man7 pages, which we are not packaging, from the staging area
to silence some warnings some are concerned about (needlessly ;-). [2]

No longer run ccache-update-links as part of post-install which, in
the world of staging, no longer is what it used to be.  Rely on the
existing @exec and @unexec in pkg-plist instead. [3]

Submitted by:	jmg [1], miwi [2]
Discussed with:	kib [1], antoine [2][3]

Remove references to long unsupported alpha.

Fix properties on pkg-plist

Update to the 20140119 snapshot of GCC 4.9.0.

Update to the 20131215 snapshot of GCC 4.9.0.

Update to the 20131208 snapshot of GCC 4.9.0.

Update to the 20131201 snapshot of GCC 4.9.0.  GCC 4.9 has now entered
stage 3 so you can expect an increase in stability, and a focus on bug
fixing.

No longer add -I${LOCALBASE}/include to CFLAGS.

Since we now configure with --with-gmp=${LOCALBASE} this is no longer
necessary, and due to bugs in binutils (which should not install ansidecl.h
into ${PREFIX}/include) and GCC (which should search its own include
directories with higher priority) can lead to build failures.

PR:		184327
Reported by:	mat, Andrzej Tobola <ato@iem.pw.edu.pl>

Change PORTNAME from gcc to gcc49 to match the actual name of this
port and avoid a package name collision with other GCC ports.  This
also allows us to remove LATEST_LINK.

On the way update to the 20131124 snapshot of GCC 4.9.0.

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

Update to the 20131020 snapshot of GCC 4.9.0.

STAGEify.

Update to the 20131013 snapshot of GCC 4.9.0.

Migrate to the new LIB_DEPENDS standard.

Add NO_STAGE all over the place in preparation for the staging support (cat:
lang)

SSP support has been added to ports with WITH_SSP for i386 and amd64
on FreeBSD 10, and amd64 on earlier versions.

SSP_UNSAFE is added to disable in a port if it fails to build, but
this should only be used in rare circumstances such as kernel modules.
Otherwise, the port may just be failing due to lack of respecting
LDFLAGS.

On FreeBSD 10, this uses an ldscript in /usr/lib/libc.so to pull in
libssp_nonshared.a to address issues linking on i386 [1].

On earlier FreeBSD versions the WITH_SSP knob will add -lssp_nonshared
to LDFLAGS on i386. This is not needed on amd64. However, several hundred
ports do not currently respect LDFLAGS, so this support is disabled currently
as it causes build failures if a dependency is looking for the stack_chk

Convert to new perl framework
Convert from USE_GMAKE to USES=gmake

Update to the 20130915 snapshot of GCC 4.9.0.

lang/gcc*: define CONFIGURE_TARGET genericly (8 ports)

Instead of hardcoding the compiler target as FreeBSD, use the OPSYS
variable to it.  This makes no practical difference for FreeBSD, but
it helps DragonFly get properly configured.

Approved by:	gerald

Introduce ICONV_CONFIGURE_ARG variable defined at Uses/iconv.mk.
It's value is "--with-libiconv-prefix=/usr/local" for systems
before 100043 with ports libiconv and to use at systems post
100043 with base iconv it's value is "" (NULL).

Co-authors:	bapt, madpilot and bsam (me)

Update to the 20130901 snapshot of GCC 4.9.0.

Update to the 20130818 snapshot of GCC 4.9.0.

Replace USE_GMAKE by USES=gmake.

- Remove MAKE_JOBS_SAFE variable

Approved by:	portmgr (bdrewery)

Update to the 20130804 snapshot of GCC 4.9.0.

Rename VERSIONSTRING to the standard DISTVERSION. [1]

Add more notes on the various variables carrying version information.

Suggested by:	crees [1]

Update to the 20130728 snapshot of GCC 4.9.0.

Introduce a new option BOOTSTRAP that allows switching between a
full bootstrap of GCC and just running a simple build.

Bootstrapping is the default upstream, and for very stable and old
flavors of GCC we disable this by default since that is a huge win
in terms of build time of the port.  No change in default behavior
for this port -- for the time being we continue to bootstrap.

Update to the 20130630 snapshot of GCC 4.9.0.

Update to the 20130609 snapshot of GCC 4.9.0.

This addresses the libitm/ build issue via an upstream of mine,
so we can remove the local patch.

Update to the 20130526 snapshot of GCC 4.9.0.  (This requires a small
adjustment to our Java hierarchy patch, no functional change though.)

Update to the 20130505 snapshot of GCC 4.9.0.

- Convert USE_ICONV=yes to USES=iconv
- Change USE_GNOME=pkgconfig|gnomehack to USES=pathfix|pkgconfig while here

Reviewed by:	zeising

Update to the 20130414 snapshot of GCC 4.9.0.  This requires a fix
for libitm which didn't expect the OS to define __always_inline by
itself (and differently).

Also, this no longer installs libffi and its info and man pages which
was always meant to remain for internal use only.

Feature safe:	yes

Now that GCC 4.8.0 has been released, welcome GCC 4.9 in its very,
very early development stages.

Business as usual with the C, C++, Fortran, Java compilers and tools
invoked as gcc49, g++49, gfortran49, gcj49 and so forth. Initially
this may be relatively stable due to the GCC 4.8.0 stabilization
efforts, but be prepared for a rough ride the coming months as this
goes through active development.