12:44 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Streamline note on building GCC itself

    322ffff

12:27 Rene Ladan (rene) 

Mk: unregister expired lang/gcc10

    3ef17f3

12:51 Rene Ladan (rene) 

Mk: unregister expired lang/gcc9

    34fa701

13:07 Lorenzo Salvadore (salvadore) 

Mk/bsd.gcc.mk: Switch USE_GCC=14 to new release port

GCC 14 first release is out and the new corresponding lang/gcc14 port
has been created with commit 4700c3f17859f7cc2c00fd5c9c7bf41e92c8142b.

Thus switch USE_GCC=14 from using lang/gcc14-devel to using lang/gcc14.

Approved by:	gerald (maintainer)

    ea25016

11:59 Lorenzo Salvadore (salvadore) 

Mk/bsd.gcc.mk: Add GCC 15 support

    b481def

20:10 Rene Ladan (rene) 

Mk/bsd.gcc.mk: unregister expired GCC 4.8

    030355a

15:15 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Use GCC 12 in examples

We want to steer people towards current versions of GCC, so use
GCC 12 in examples over GCC 10 and GCC 11 now that the default is
GCC 13.

    95ead80

00:06 Muhammad Moinur Rahman (bofh) 

lang/gcc8: Remove expired port

2023-12-31 lang/gcc8: Unsupported by upstream. Use GCC 11 or newer instead.

    8738260

12:46 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Streamline test-gcc output

Remove BUILD_DEPENDS and RUN_DEPENDS from the output of test-gcc.
These two are more general and can be easily be shown via 'make -V'.

    6a79b44

13:03 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Simplify logic, only dealing with ports

We now only have to deal with GCC from ports, not base any longer.
So strip a check that has been a no-op for a while (as evidenced by
_GCC_PORT always being set directly above).

    a893761

17:57 Lorenzo Salvadore (salvadore) 

Mk/bsd.gcc.mk: Add GCC 14

- Add USE_GCC=14, which introduces a dependency on lang/gcc14-devel.
- Switch USE_GCC=13 from lang/gcc13-devel to lang/gcc13.

Reviewed by:	vishwin
Approved by:	gerald (maintainer)
Differential Revision: https://reviews.freebsd.org/D39878

    aa8e844

00:34 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Remove support for USE_GCC=X+

At this point most ports that employ USE_GCC have the USE_GCC=yes
form, some have USE_GCC=X (where X is an older version of GCC than
the current default), and none is left with USE_GCC=X+.

To reduce complexity and since we are actively tracking upstream GCC
with our default version, remove support for the USE_GCC=X+ form.

This also derisks Mk/Uses/fortran.mk which aligns with USE_GCC after
commit 4191c71fbd229e5a96382bc6fa271a1ce5668b0f. [1]

PR:		266196 [1]

    9b5f5ab

19:40 Tobias C. Berner (tcberner) 

cleanup: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  Akinori MUSHA <knu@FreeBSD.org>
  *  Alejandro Pulver <alepulver@FreeBSD.org>
  *  Edwin Groothuis <edwin@freebsd.org>
  *  Ernst de Haan <znerd@FreeBSD.org>
  *  Florent Thoumie <flz@FreeBSD.org>
  *  Gabor Kovesdan <gabor@FreeBSD.org>
  *  Mark Linimon <linimon@FreeBSD.org>
  *  Shaun Amott <shaun@inerd.com>

With hat:	portmgr
Reported by:	mat

    2c54d26

23:43 Piotr Kubaj (pkubaj) 

Mk/bsd.gcc.mk: only use -devel port for 13

Reported by:	Mark Millard

    2fdf14d

07:26 Piotr Kubaj (pkubaj) 

lang/gcc13-devel: Add port

Add new port to track the latest development branch of GCC.

    0921161

10:00 Tobias C. Berner (tcberner) 

framework: cleanup conditional-indentations in Mk/

Run Tools/scripts/indent_make_if.pl on all of Mk.

These white space changes contribute greatly to the readability of those files.
As we have a version control system, finding out the reasons for the changes
prior to these white space changes is still easily possible

Differential Revision:	https://reviews.freebsd.org/D35024
Reviewed by:		portmgr (rene, bapt)

    aa25396

17:47 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Remove USE_GCC=any

We have recommended against USE_GCC=any for a while, and as of more
recently it was completely equivalent to USE_GCC=yes.

With (ancient versions of) GCC hardly available in the base system
of FreeBSD systems at this point, there's unlikely to be a use case
to reintroduce it, so remove the few remaining traces.

PR:		258015

    3d1ff1f

18:20 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Strongly discourage USE_GCC=any

PR:		258015

    e6d30d6

12:39 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: User newer versions in examples

    3716b29

06:41 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Remove support for GCC 7

GCC 7 is way beyond end of life (with even GCC 8 end of life at
this point) and no port in the tree still has USE_GCC=7.

    96bb592

07:25 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Adjust to the release of GCC 11

Now that GCC 11.1 has been released and lang/gcc11 is in place,
have USE_GCC=11 use that instead of lang/gcc11-devel.

In addition add support for USE_GCC=12 which uses lang/gcc12-devel
(still in early development, not recommended for production use).

    8e7d39d

08:45 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Never use /usr/bin/gcc

USE_GCC=any was introduced to leverage the old version of GCC 4.2
installed as /usr/bin/gcc on some systems. That has increasingly
not been present any longer (not on i386 and amd64 since 12.x and
optionally 11.x, not even on the ppcdevref system according to
linimon@) and hardly anyone actually has been testing ports in
this scenario.

So, finally stop using /usr/bin/gcc (and /usr/bin/gc++ and
/usr/bin/gcpp) even if present.

This makes USE_GCC=any just another way of spelling USE_GCC=yes
before we finally de-orbit it.

Discussed with: mat, linimon, pkubaj

    96c1763

13:57 Gerald Pfeifer (gerald) 

Mk/bsd.gcc.mk: Deprecate USE_GCC=any

    768f18f

14:27 Mathieu Arnold (mat) 

framework: Remove $FreeBSD$

Where appropriate fiddle with a few other things.

    5d33e04

15:15 gerald 

In some cases one may want to use GCC to build something when its
runtimes or GCC at runtime are not required.

Introduce an optional argument for USE_GCC that indicates GCC is
only required at build time.

Examples for the new syntax are USE_GCC=yes:build, USE_GCC=9:build,
or USE_GCC=11+:build.

Submitted by:	Fabian Freyer <fabian.freyer@physik.tu-berlin.de>
PR:		211154
Differential Revision:	https://reviews.freebsd.org/D7223

 

21:57 gerald 

Simplify a comment after r531883 | gerald | 2020-04-16 (which in turn
simplified the structure of Mk/bsd.gcc.mk).

 

08:49 gerald 

Now that GCC 10.1 has been released and lang/gcc10 arrived to track
GCC 10 releases, switch to that over lang/gcc10-devel when GCC 10 is
requested.

Use lang/gcc11-devel when GCC 11 is requested, but note that this is
absolutely experimental and subject to constant change and likely
breakage over the next half year at least before that release series
enters stabilization.  Use at your own risk.

 

14:20 gerald 

Add support for GCC 10.  That is in the release phase and has not seen
an upstream release yet, so we need to leverage the gcc10-devel port
which we'll replace by gcc10 once that exists.

This is not intended for production use, but to allow for an -exp run
and preparing other ports.

 

22:25 gerald 

Finalize the streamlining of data structures holding version-specific
information in the light of us only encountering at most one version
(GCC 4.2) in the base system these days.

 

20:43 gerald 

Simplify the logic by removing a variable (_GCC_PORT_DEPENDS) and
instead use two equivalent ones (depending on the circumstances).

 

21:46 gerald 

Refactor the handling of USE_GCC=any so that it essentially becomes a
block of its own as opposed to touching bits and pieces throughout.

Use the opportunity to simplify various aspects, such as the static
tables describing versions of GCC we support and their initialization.

Overall this sheds another 30 lines off what used to me more tricky
Makefile code.  It should not change behavior.

 

09:03 gerald 

Streamline two comments and remove debugging output we hardly need any
longer (and will need even less shortly).

 

10:15 gerald 

Significantly simplify the logic to determine which port (or base version)
of GCC to use based on the specification of USE_GCC.

This is based on the observation that we now only have a single version
of GCC in base, namely GCC 4.2, which is not in ports any longer.  And
we limit our choice to either the specific version requested or the
default version of GCC in the ports tree; i.e., we no longer consider
an installed port of any version in between (which is a fringe case
extremely few, if any, users would have experienced, and then only
outside a clean build environment in any case).

Streamline some debugging output accordingly.

Overall this removes some 25 lines of largely complex logic.

 

03:06 gerald 

With print/pdftk which required GCJ (GNU Java) updated, the last
dependency on GCC 6 in the Ports Collection is gone, so we can remove
support for USE_GCC=6 and USE_GCC=6+. [1]

This does not remove lang/gcc6 yet, but helps avoid new dependencies,
and GCC 6 has been unmaintained upstream for more than a year.

On the way update two examples to use more current versions of GCC.

Thanks to:	tobik [1]

 

07:55 gerald 

Add support for GCC 9 via the new lang/gcc9 port.  USE_GCC=9+ and
USE_GCC=9 (the latter of which should only be used if unavoidable)
are now supported.

 

07:03 gerald 

Now that the last dependency on GCC 5 (and lang/gcc5) in the Ports
Collection is gone, remove USE_GCC=5 as an option.

This does not remove lang/gcc5 as such, but helps avoid new dependencies
creeping in, in particular since GCC 5 has been unmaintained upstream for
a while.

 

06:10 gerald 

Remove support for USE_GCC=4.9+ and USE_GCC=4.9 from the tree.  Nothing
depends on it any longer (and has for a while) and GCC 4.9 went end of
life upstream in summer 2016.

 

15:38 andreast 

Fix build of GCC on powerpc64.

While building GCC itself we have to use the built GCC libraries to configure
additional parts of GCC and not the libraires from the host.

Install the built 32-bit libraries. This was not done up to now.

PR:	231804
Approved by:	gerald@

 

13:30 gerald 

Filter -mretpoline, which is specific to clang and not supported by
GCC, from CFLAGS and CXXFLAGS.

This also establishes a good place where to add any additional such
cases in the future.

PR:		230200
Submitted by:	rozhuk.im@gmail.com

 

12:14 gerald 

Add CXXFLAGS to the debugging output provided by test-gcc and put that,
as well as the existing output for CFLAGS, on a line of its own to make
this easier to parse.

 

05:59 gerald 

Add support for GCC 8 (and the newly added lang/gcc8 port).  USE_GCC=8+
is now feasible, for example.

PR:		229681
Submitted by:	mi

 

08:03 gerald 

Document the form USE_GCC=X+ instead of the older form USE_GCC=X.Y+
that has been necessary for the GCC 4.x series and should not see any
new usage anways.

Use more current versions of GCC in examples, choosing the two most
realistic options.

 

12:44 gerald 

Connect the new lang/gcc7 port into the infrastructure of Mk/bsd.gcc.mk
(providing USE_GCC) and Mk/bsd.default-versions.mk.

PR:		220794

 

02:15 gerald 

Remove support for USE_GCC=4.7 and USE_GCC=4.7+.  Nothing in the tree
uses it and GCC 4.7 has been end-of-lifed upstream years ago.

The lang/gcc47 port itself is still in place and can be used.

 

05:40 gerald 

As of today, USE_GCC=yes (and USE_GCC=any in most circumstances)
and consequently many of the USES=compiler flavors use the canonical
version of GCC as defined in Mk/bsd.default-versions.mk as well as
the lang/gcc port

With the "new" setup starting with GCC 5 where I have introduced
lang/gcc5-devel for regular snapshots and lang/gcc5 for releases,
and similarly for GCC 6 and onward, we can now leverage lang/gcc5
(and later) for most of the role that lang/gcc used to play -- and
indeed as of today lang/gcc and lang/gcc5 are nearly identical
short of symlinks for gcc, g++, and gfortran binaries that the
former provides.

So now use lang/gcc5 instead of lang/gcc whenever requested via the
USE_GCC framework directly or indirectly.

This is similar to how the python ports work, for example, and it
allows simplifications in Mk/bsd.gcc.mk and Mk/Uses/fortran.mk and
dropping LANG_GCC_IS from Mk/bsd.default-versions.mk.  As a next
step lang/gcc is going to become a "hull" essentially only providing
those symlinks and requiring lang/gcc5 (or whatever has been set as
default in Mk/bsd.default-versions.mk).

 

19:45 gerald 

Use USE_GCC=6+ as example for the "+" flavor of USE_GCC instead of
USE_GCC=4.9+.  Among others, this adds an example for the new, single
digit GCC versions.

 

22:59 gerald 

Remove 4.6 as a valid option for USE_GCC and GCC_DEFAULT; it has not
been used in the Ports Collection for quarters and hardly would make
sense (or even work) as default GCC version.

 

12:09 mat 

Always include bsd.default-versions.mk in bsd.port.mk.

The variable defined in it are now always available after including
bsd.port.pre.mk.

PR:		210666
Submitted by:	mat
Exp-run by:	antoine
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D6933

 

09:11 gerald 

Now that lang/gcc6 has landed (which carries official GCC 6.x releases),
add support for USE_GCC=6 and USE_GCC=6+.

 

13:34 mat 

Try to be more helpful to our users, and keep all the possible versions
close to their default value in Mk/bsd.default-versions.mk.

Sponsored by:	Absolight

 

01:23 bapt 

Remove the now unneeded ${PORTSDIR} from dependency definition in
The infrastructure Makefiles

PR:		206569
Exp run by:	antoine
Differential Revision:	D5047

 

21:29 gerald 

Since there is not going to be any new version of GCC in the FreeBSD
base system ever again, simplify the GCCVERSION table and logic to not
worry about minimum system versions carrying a certain version of GCC.

This also removes the _GCCVERSION_${v}_R variables and simplifies some
logic and debug output.

 

00:03 gerald 

Move LANG_GCC_IS from bsd.gcc.mk to bsd.default-versions.mk and use
this and GCC_DEFAULT instead of hard-coding the version of GCC used
by lang/gcc in Uses/fortran.mk.

Approved by:	portmgr (antoine)

 

09:29 gerald 

Rename the somewhat confusingly named GCC_DEFAULT_V to LANG_GCC_IS.
(The regular GCC_DEFAULT is still set in bsd.default-versions.mk.)

 

14:25 gerald 

Update examples to use GCC 4.9 instead of 4.8, since the latter is now
the default version anyway.

 

21:15 gerald 

Add support for USE_GCC=5 and its preferred form USE_GCC=5+.

PR:		194676

 

16:00 tijl 

Depend on lang/gccXY if users wish to use a different version of gcc by
default than lang/gcc (currently 4.8).

(I don't fully agree with this implementation but this makes something
like DEFAULT_VERSIONS+=gcc=4.9 in make.conf work correctly.)

Reported by:	Luca Pizzamiglio <luca.pizzamiglio@gmail.com>
Approved by:	gerald

 

00:45 gerald 

Refer to bsd.default-versions.mk for the canonical version of GCC; no
longer duplicate version information related to that.

 

20:41 gerald 

Update the default version of GCC used in the Ports Collection from
GCC 4.6.4 to GCC 4.7.3.  This entails updating the lang/gcc port as
well as changing the default in Mk/bsd.default-versions.mk.

This adds powerpc64 as a supported architecture (and removes ia64,
though it can be supported by manually installing lang/gcc48).

New binaries %%GNU_HOST%%-gcc-ar47, %%GNU_HOST%%-gcc-nm47, and
%%GNU_HOST%%-gcc-ranlib47 are provided to support link-time
optimization (LTO) which scales significantly better.

And it adds support for indirect functions (IFUNCS), experimental
support for transactional memory in the compiler as well as a supporting
run-time library called libitm, a new string length optimization pass,
and support for atomic operations specifying the C++11/C11 memory model.

Version 3.1 of the OpenMP specification is now supported for the C,
C++, and Fortran compilers.

GCC accepts the options -std=c11 and -std=gnu11 for the C11 revision
of the ISO C standard which inlcude support for unicode strings,
nonreturning functions (_Noreturn and <stdnoreturn.h>), alignment
support (_Alignas, _Alignof, max_align_t, <stdalign.h>), and a
__builtin_complex built-in function.

The C++ frontend now accepts the -std=c++11, -std=gnu++11, and
-Wc++11-compat options and implements many C++11 features of the
language including extended friends syntax, explicit override
control, non-static data member initializers, user-defined literals,
alias declarations, delegating constructors, atomic classes, and more.

The C++ standard library and Fortran frontend have received many
improvements.  See http://gcc.gnu.org/gcc-4.7/changes.html for an
extense list of changes; http://gcc.gnu.org/gcc-4.7/porting_to.html
for information on how to port to that new version.

PR:		182136
Supported by:	Christoph Moench-Tegeder <cmt@burggraben.net> (fixing many ports)
Tested by:	bdrewery (two -exp runs)

 

00:36 gerald 

Revert bogus parts of revision 345909.

 

00:32 gerald 

Reword the documentation at the top of this file.

Sort the FPC_DEFAULT and GCC_DEFAULT entries.

 

22:15 gerald 

Replace all uses of GCC_DEFAULT_VERSION by GCC_DEFAULT, remove the
definition of the former from Mk/bsd.gcc.mk and add the latter --
still set to 4.6 -- to Mk/bsd.default-versions.mk.

Include Mk/bsd.default-versions.mk from Mk/bsd.gcc.mk to tie the
two together.

 

02:20 gerald 

Remove the _GCC_BUILD_DEPENDS variable which we had kept for the sake
of some ports using this unexpectedly.  There are no further instances
in the tree any more.

If there is an absolute need to refer to the GCC runtime directory that
cannot be covered by CFLAGS, LDFLAGS or the like, use _GCC_RUNTIME.
This hardly ever should be necessary, though.  Avoid whenever possible!

 

17:15 tijl 

Convert all USE_FORTRAN=yes to "USES=fortran, USE_GCC=yes".  In most cases
USE_GCC=yes has been omitted though.

Remove USE_FORTRAN handling from bsd.port.mk and bsd.gcc.mk.

Minor cleanups in some ports like USE_GMAKE, NOPORTDOCS,...

Exp-run:	bdrewery
Approved by:	portmgr (bdrewery)

 

16:33 rene 

Unregister lang/gcc44 now that it is no longer used by any port.

Approved by:	gerald

 

15:12 mat 

Fixup svn props in Mk.

Sponsored by:	Absolight

 

15:49 rene 

Disconnect lang/gcc34 from bsd.gcc.mk, it is not used by any port anymore.
This also removes the g77 option of USE_FORTRAN, and USE_GCC now always
implies a dependency on binutils.

Reviewed by:	bapt
Approved by:	maintainer (gerald)

 

22:36 gerald 

Explicitly include the GCC run time directory in LDFLAGS.  This should
not be necessary when linking with GCC, but that's not the only way the
link process can be invoked.

PR:		182136

 

10:19 gerald 

Unbreak USE_GCC=any.  We do need to keep GCC 4.2 in our internal tables
for that, even if lang/gcc42 is gone.

Tested on systems with and without GCC in base.

Reported by:	Terry Kennedy <TERRY@tmk.com>, dbn

 

01:21 gerald 

Bye, bye lang/gcc42 aka GCC 4.2.  As a port you have served us well,
but six-and-a-half years after the upstream release of GCC 4.2.0 and
exactly two years after the removal of lang/gcc45 the time has come.

This reduces package name collisions around GCC related ports by 12.5%. [1]

Reported by:	bapt [1]

 

20:29 gerald 

Document USE_GCC=any.  Reformat the description a bit and use newer
versions of GCC for reference.

 

21:23 gerald 

Add support for USE_GCC=4.9 and USE_GCC=4.9+.

Beware, this version of GCC is _not_ anywhere near ready for production
use.  Use at your own risk, and rather don't use it for regular ports.

Submitted by:	devzone.my@gmail.com

 

11:26 gerald 

Merge two loops and initialize _GCC_FOUND${v} and check whether USE_GCC
points to a valid version in parallel.

 

18:37 gerald 

When the same version of GCC is present as a port and in base, prefer
the former.

Improve consistency of the code in on place.

 

13:01 gerald 

Simplify (and strictly speaking, though not practically given version
number schemes between FreeBSD and GCC, correct) the check for a valid
version specified by USE_GCC. [1]

If IGNORE is set, have test-gcc note that instead of showing its usual,
and in that case incorrect and useless, debugging output.

PR:		175252 [1]
Submitted by:	Yamaya Takashi <yamayan@kbh.biglobe.ne.jp> [1]

 

03:21 gerald 

Do not just rely on the version number of FreeBSD in deciding whether
a certain version of GCC is in the base, but also check the existence
of /usr/bin/gcc.

This unbreaks systems where GCC is not built as part of the world, and
instead relies on versions of GCC in the Ports Collection there.

PR:		175252
Submitted by:	Yamaya Takashi <yamayan@kbh.biglobe.ne.jp>

 

01:06 gerald 

Remove a bogus old check that assumes that every version of FreeBSD has
GCC in the base.

Adjust a comment, now describing the real purpose of the code remaining
in that block.

PR:		175252

 

23:25 bapt 

Fix when bsd.gcc.mk is included and USE_GCC is undefined for example in case a
port use USE_FORTRAN

 

21:35 gerald 

Add a new form of USE_GCC, USE_GCC=yes, which generically requests
a current version of GCC.  This reduces churn for individual ports
and further increases consistency (in line with a canonical version
that we introduced with GCC_DEFAULT_VERSION earlier on and the older
USE_FORTRAN=yes).

On the way, make some comments more consistent.

Discussed with:	linimon

 

00:23 gerald 

In addition to CFLAGS and LDFLAGS now also CXXFLAGS set an rpath to
the GCC run-time.

This extends revision r246991 (2010-01-02) and should not be necessary
in most cases since LDFLAGS already covers linking, but one can always
compile and link in one swoop, and this makes things consistent between
C and C++.

Feature safe:	yes

 

19:33 linimon 

Introduce the new semantic USE_GCC=any, which can be set in any port
Makefile.  For systems where CC is gcc, this has no effect.  For systems
where CC is clang, this forces the use of the base GCC suite.  (Some
forward compatibility is also covered in the patch.)

Confirmed to have no ill-effects via multiple runs with gcc as CC:

 
http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-errorlogs/e.8-exp-bcm.20121006012556.pointyhat-west/

and clang as CC:

 
http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp-clang.20121005165436.pointyhat-west/

This change is necessary (but insufficient) for the upcoming switch to
clang as CC for the tier-1 architectures.

Finally, accept FORCE_BASE_CC_FOR_TESTING as an override for USE_GCC,
for those who wish to help debug ports with clang.  It is an absolute
override; it overrides not only the value "any" but also any value such
as "4.4+".

Reviewed by:	brooks, gerald
Approved by:	maintainer (gerald)

 

21:23 gerald 

Introduce _GCC_RUNTIME, to be used by ports in need of knowing the
run-time directory of the version of GCC in use.

As a side effect this fixes the inclusion of said directory into
CFLAGS and LDFLAGS (and FFLAGS where applicable). [1]

Reported by:	Scott Allendorf <scott-allendorf@uiowa.edu> [1]

16:23 gerald 

Add support for USE_GCC=4.8, USE_GCC=4.8+, and generally detect
and consider lang/gcc48 if present.

Submitted by:	kwm

02:28 gerald 

Use the stable, slow moving lang/gcc instead of lang/gcc46 for
USE_GCC=4.6 and USE_GCC=4.6+ and generally whenever the default
version of GCC is employed.

This will significantly benefit tinderboxes and the larger, reasonably
conservative user base by reducing the amount of rebuilds.

Rename _GCC_BUILD_DEPENDS to _GCC_PORT, but still set _GCC_BUILD_DEPENDS
in the end for the sake of some ports relying on that.

PR:		169449
Discussed with:	bf

13:54 sunpoet 

- Revert accidental commit

13:42 sunpoet 

- Add shared TLS description

08:17 miwi 

- Remove emacs mode, -*- mode: ...; -*- [1]
- Comments for BUILD_ and RUN_DEPENDS fail to mention alternate means to specify
dependencie [2]
- Fix make reinstall [3]
- Trivial comment change for PORTDATA [4]

PR:             151954 [1]
                161314 [2]
                167085 [3]
                167465 [4]
Submitted by:   Anonymous <swell.k@gmail.com> [1]
                dougb@ and Chris Rees <utisoft@gmail.com> [2]
                Garrett Cooper <yanegomi@gmail.com> [3]
                "Bryan Drewery" <bryan@shatow.net> [4]
Tested via:     phw

12:20 gerald 

Remove last reference to GCC 4.5 now that no port refers to it any more.

22:03 gerald 

Disconnect GCC 4.5 alias lang/gcc45.

No ports uses this directly any more via USE_GCC=4.5 and for the sake
of those nine that have USE_GCC=4.5+ we transparently rewrite this to
USE_GCC=4.6+ which has already happened for weeks for tinderbox builds.

Feature safe:   yes

20:58 gerald 

Fix mis-applied patch from revision 1.59 (moving the new code one
conditional up).

Discussed with: bf

15:51 gerald 

Refer to GCC 4.7 instead of GCC 4.5.  Mark the part that should not see
changes based on GCC changes more clearly.

01:34 gerald 

When USE_GCC=X.Y+ has been specified, prefer the default version of
GCC (the one which also USE_FORTRAN=yes chooses) in case we do have
to install GCC in any case.  Only if an acceptable version of GCC
is already present use that one.

This will ease the load on tinderboxes, further the use of current
versions of GCC, and minimize the need to download/carry several
versions of GCC for users of pre-built packages.

PR:             160507
Submitted by:   bf

08:17 gerald 

Fix the previous commit for the case where USE_FORTRAN is undefined.

Pointy hat to:  self, bf

07:37 gerald 

Reference the GCC run-time libraries via FFLAGS, too, in addition to
CFLAGS and LDFLAGS, if USE_FORTRAN=yes has been specified.

Submitted by:   bf

00:40 gerald 

Make USE_FORTRAN=yes imply the use of GCC 4.6 over GCC 4.5 so far.

Exp-run by:     pav
Thanks to:      pav, bf (for fixing several ports)

12:10 gerald 

Cater to versions of FreeBSD greater than 9 (up to 99). [1]

Tweak the representation of versions of GCC that newer appeared in base.

Submitted by:   bf [1]

16:56 gerald 

Refer to GCC 4.2+ instead of GCC 3.4+ in a comment, since the latter is
not in any supported release of FreeBSD any more.

22:40 gerald 

Clean up after revision 1.51 and adjust comments to the new reality of us
not caring about FreeBSD <= 6 any more (and thus no g77 in base ever).

21:16 gerald 

Add support for USE_GCC=4.7, USE_GCC=4.7+ and notably an installation of
lang/gcc47 being used when USE_GCC=4.5+ or the like is specified.

PR:             159036
Submitted by:   kalten@gmx.at

22:33 flz 

Latest round of infrastructure changes.

- bsd.port.mk: add INDEX_PORTS, to support INDEX creation for a subset of the
ports tree [1]
- bsd.port.mk: call target "install-rc-script" before "post-install" [2]
- [patch] ports/Mk bsd.port.mk order if groups/users are created by package [3]
- [bsd.port.mk] [patch] reaper of the dead: md5 has been in /sbin for a while
[4]
- [bsd.port.mk] [patch] remove support for pre 7.x systems (b.*.m) [5]
- [patch] [bsd.port.mk] reaper of the dead: are three variable defintions needed
[6]

PR:             ports/156575 [1],
                ports/139116 [2],
                ports/152498 [3],
                ports/155983 [4],
                ports/155510 [5],
                ports/156340 [6]
Submitted by:   Florent Thoumie <flz@xbsd.org> [1],
                Sergey Skvortsov <skv@freebsd.org> [2],
                Olli Hauer <ohauer@FreeBSD.org> [3],
                Eitan Adler <lists@eitanadler.com> [4],
                Eitan Adler <lists@eitanadler.com> [5],
                Eitan Adler <lists@eitanadler.com> [6]