notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)

Current status

The server has been repaired, with a new power supply, for $23. I am waiting for lower COVID rates before visiting the datacenter to return it.
VUXML processing is halted. All vuln information is out of date.
non port: Mk/

Number of commits found XX: 125 (showing only 100 on this page)

1 | 2  »  

Sat, 20 Jun 2020
[ 21:57 gerald ] Original commit   Revision:539753
539753 Mk/
Simplify a comment after r531883 | gerald | 2020-04-16 (which in turn
simplified the structure of Mk/
Tue, 2 Jun 2020
[ 08:49 gerald ] Original commit   Revision:537529
537529 Mk/
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

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.
Sun, 26 Apr 2020
[ 14:20 gerald ] Original commit   Revision:533066
533066 Mk/
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.
Thu, 16 Apr 2020
[ 22:25 gerald ] Original commit   Revision:531883
531883 Mk/
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.
Thu, 9 Apr 2020
[ 20:43 gerald ] Original commit   Revision:531271
531271 Mk/
Simplify the logic by removing a variable (_GCC_PORT_DEPENDS) and
instead use two equivalent ones (depending on the circumstances).
Fri, 3 Apr 2020
[ 21:46 gerald ] Original commit   Revision:530527
530527 Mk/
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.
Thu, 12 Mar 2020
[ 09:03 gerald ] Original commit   Revision:528279
528279 Mk/
Streamline two comments and remove debugging output we hardly need any
longer (and will need even less shortly).
Sat, 22 Feb 2020
[ 10:15 gerald ] Original commit   Revision:526751
526751 Mk/
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.
Tue, 31 Dec 2019
[ 03:06 gerald ] Original commit   Revision:521584
521584 Mk/
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]
Sun, 2 Jun 2019
[ 07:55 gerald ] Original commit   Revision:503289
503289 Mk/
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.
Sat, 18 May 2019
[ 07:03 gerald ] Original commit   Revision:501916
501916 Mk/
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.
Sat, 23 Feb 2019
[ 06:10 gerald ] Original commit   Revision:493645
493645 Mk/
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.
Sat, 29 Dec 2018
[ 15:38 andreast ] Original commit   Revision:488673
488673 Mk/
488673 lang/gcc7/Makefile
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@
Sun, 5 Aug 2018
[ 13:30 gerald ] Original commit   Revision:476413
476413 Mk/
Filter -mretpoline, which is specific to clang and not supported by

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

PR:		230200
Submitted by:
[ 12:14 gerald ] Original commit   Revision:476411
476411 Mk/
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.
Sun, 15 Jul 2018
[ 05:59 gerald ] Original commit   Revision:474663
474663 Mk/
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
Sat, 2 Jun 2018
[ 08:03 gerald ] Original commit   Revision:471347
471347 Mk/
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.
Tue, 15 Aug 2017
[ 12:44 gerald ] Original commit   Revision:447982
447982 Mk/
447982 Mk/
Connect the new lang/gcc7 port into the infrastructure of Mk/
(providing USE_GCC) and Mk/

PR:		220794
Mon, 5 Jun 2017
[ 02:15 gerald ] Original commit   Revision:442601
442601 Mk/
442601 Mk/
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.
Tue, 2 May 2017
[ 05:40 gerald ] Original commit   Revision:439929
439929 Mk/Uses/
439929 Mk/
439929 Mk/
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/ 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/ and Mk/Uses/ and
dropping LANG_GCC_IS from 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/
Wed, 1 Feb 2017
[ 19:45 gerald ] Original commit   Revision:433084
433084 Mk/
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.
Sat, 28 Jan 2017
[ 22:59 gerald ] Original commit   Revision:432693
432693 Mk/
432693 Mk/
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.
Wed, 3 Aug 2016
[ 12:09 mat ] Original commit   Revision:419511
419511 Mk/Uses/
419511 Mk/Uses/
419511 Mk/Uses/
419511 Mk/Uses/
419511 Mk/Uses/
419511 Mk/Uses/
419511 Mk/Uses/
419511 Mk/Uses/
419511 Mk/Uses/
419511 Mk/Uses/

(Only the first 10 of 17 ports in this commit are shown above. View all ports for this commit)
Always include in

The variable defined in it are now always available after including

PR:		210666
Submitted by:	mat
Exp-run by:	antoine
Sponsored by:	Absolight
Differential Revision:
Fri, 10 Jun 2016
[ 09:11 gerald ] Original commit   Revision:416663
416663 Mk/
Now that lang/gcc6 has landed (which carries official GCC 6.x releases),
add support for USE_GCC=6 and USE_GCC=6+.
Thu, 14 Apr 2016
[ 13:34 mat ] Original commit   Revision:413261
413261 Mk/Uses/
413261 Mk/Uses/
413261 Mk/Uses/
413261 Mk/Uses/
413261 Mk/Uses/
413261 Mk/Uses/
413261 Mk/Uses/
413261 Mk/
413261 Mk/
413261 Mk/

(Only the first 10 of 14 ports in this commit are shown above. View all ports for this commit)
Try to be more helpful to our users, and keep all the possible versions
close to their default value in Mk/

Sponsored by:	Absolight
Sun, 27 Mar 2016
[ 01:23 bapt ] Original commit   Revision:411970
411970 Mk/Uses/
411970 Mk/Uses/
411970 Mk/Uses/
411970 Mk/Uses/
411970 Mk/Uses/
411970 Mk/Uses/
411970 Mk/Uses/
411970 Mk/Uses/
411970 Mk/Uses/
411970 Mk/Uses/

(Only the first 10 of 85 ports in this commit are shown above. View all ports for this commit)
Remove the now unneeded ${PORTSDIR} from dependency definition in
The infrastructure Makefiles

PR:		206569
Exp run by:	antoine
Differential Revision:	D5047
Wed, 22 Apr 2015
[ 21:29 gerald ] Original commit   Revision:384521
384521 Mk/
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.
Mon, 26 Jan 2015
[ 00:03 gerald ] Original commit   Revision:377909
377909 Mk/Uses/
377909 Mk/
377909 Mk/
Move LANG_GCC_IS from to and use
this and GCC_DEFAULT instead of hard-coding the version of GCC used
by lang/gcc in Uses/

Approved by:	portmgr (antoine)
Sun, 4 Jan 2015
[ 09:29 gerald ] Original commit   Revision:376187
376187 Mk/
Rename the somewhat confusingly named GCC_DEFAULT_V to LANG_GCC_IS.
(The regular GCC_DEFAULT is still set in
Fri, 7 Nov 2014
[ 14:25 gerald ] Original commit   Revision:372268
372268 Mk/
Update examples to use GCC 4.9 instead of 4.8, since the latter is now
the default version anyway.
Sun, 2 Nov 2014
[ 21:15 gerald ] Original commit   Revision:372091
372091 Mk/
Add support for USE_GCC=5 and its preferred form USE_GCC=5+.

PR:		194676
Fri, 26 Sep 2014
[ 16:00 tijl ] Original commit   Revision:369328
369328 Mk/Uses/
369328 Mk/
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 <>
Approved by:	gerald
Sun, 16 Mar 2014
[ 00:45 gerald ] Original commit   Revision:348390
348390 Mk/
Refer to for the canonical version of GCC; no
longer duplicate version information related to that.
Mon, 10 Mar 2014
[ 20:41 gerald ] Original commit   Revision:347808
347808 Mk/
347808 Mk/
347808 lang/gcc/Makefile
347808 lang/gcc/distinfo
347808 lang/gcc/files/patch-unwind-ia64.h
347808 lang/gcc/pkg-descr
347808 lang/gcc/pkg-plist
347808 lang/gcc47/Makefile
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/

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.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
Tue, 25 Feb 2014
[ 00:36 gerald ] Original commit   Revision:345910
345910 Mk/Uses/
345910 Mk/
Revert bogus parts of revision 345909.
[ 00:32 gerald ] Original commit   Revision:345909
345909 Mk/Uses/
345909 Mk/
345909 Mk/
Reword the documentation at the top of this file.

Sort the FPC_DEFAULT and GCC_DEFAULT entries.
Mon, 24 Feb 2014
[ 22:15 gerald ] Original commit   Revision:345903
345903 Mk/
345903 Mk/
Replace all uses of GCC_DEFAULT_VERSION by GCC_DEFAULT, remove the
definition of the former from Mk/ and add the latter --
still set to 4.6 -- to Mk/

Include Mk/ from Mk/ to tie the
two together.
Sun, 23 Feb 2014
[ 02:20 gerald ] Original commit   Revision:345690
345690 Mk/
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!
Sun, 16 Feb 2014
[ 17:15 tijl ] Original commit   Revision:344614
344614 Mk/Uses/
344614 Mk/Uses/
344614 Mk/
344614 Mk/
344614 Mk/
344614 benchmarks/himenobench/Makefile
344614 benchmarks/hpl/Makefile
344614 benchmarks/octave-forge-benchmark/Makefile
344614 biology/crux/Makefile
344614 biology/plink/Makefile

(Only the first 10 of 211 ports in this commit are shown above. View all ports for this commit)
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 and

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

Exp-run:	bdrewery
Approved by:	portmgr (bdrewery)
Sun, 26 Jan 2014
[ 16:33 rene ] Original commit   Revision:341241
341241 Mk/
Unregister lang/gcc44 now that it is no longer used by any port.

Approved by:	gerald
Wed, 22 Jan 2014
[ 15:12 mat ] Original commit   Revision:340713
340713 Mk/Scripts/
340713 Mk/Scripts/pkgencode.awk
340713 Mk/Uses/
340713 Mk/
340713 Mk/
340713 Mk/
340713 Mk/
340713 Mk/
340713 Mk/
340713 Mk/

(Only the first 10 of 19 ports in this commit are shown above. View all ports for this commit)
Fixup svn props in Mk.

Sponsored by:	Absolight
Sat, 4 Jan 2014
[ 15:49 rene ] Original commit   Revision:338649
338649 Mk/
Disconnect lang/gcc34 from, 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)
Sat, 7 Dec 2013
[ 22:36 gerald ] Original commit   Revision:335855
335855 Mk/
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
Sat, 23 Nov 2013
[ 10:19 gerald ] Original commit   Revision:334653
334653 Mk/
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 <>, dbn
[ 01:21 gerald ] Original commit   Revision:334629
334629 MOVED
334629 Mk/
334629 lang/Makefile
334629 lang/gcc42
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]
Sun, 10 Nov 2013
[ 20:29 gerald ] Original commit   Revision:333442
333442 Mk/
Document USE_GCC=any.  Reformat the description a bit and use newer
versions of GCC for reference.
Sun, 13 Oct 2013
[ 21:23 gerald ] Original commit   Revision:330254
330254 Mk/
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:
Fri, 29 Mar 2013
[ 11:26 gerald ] Original commit   Revision:315538
315538 Mk/
Merge two loops and initialize _GCC_FOUND${v} and check whether USE_GCC
points to a valid version in parallel.
Tue, 19 Mar 2013
[ 18:37 gerald ] Original commit   Revision:314673
314673 Mk/
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.
Sat, 16 Mar 2013
[ 13:01 gerald ] Original commit   Revision:314352
314352 Mk/
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 <> [1]
Sun, 3 Mar 2013
[ 03:21 gerald ] Original commit   Revision:313323
313323 Mk/
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 <>
Sat, 2 Mar 2013
[ 01:06 gerald ] Original commit   Revision:313177
313177 Mk/
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
Sat, 22 Dec 2012
[ 23:25 bapt ] Original commit   Revision:309408
309408 Mk/
Fix when is included and USE_GCC is undefined for example in case a
port use USE_FORTRAN
[ 21:35 gerald ] Original commit   Revision:309406
309406 Mk/
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

On the way, make some comments more consistent.

Discussed with:	linimon
Tue, 6 Nov 2012
[ 00:23 gerald ] Original commit   Revision:307045
307045 Mk/
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
Sun, 7 Oct 2012
[ 19:33 linimon ] Original commit   Revision:305504
305504 Mk/
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:

and clang as CC:

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)
Fri, 3 Aug 2012
[ 21:23 gerald ] Original commit 
301973 Mk/
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 <> [1]
[ 16:23 gerald ] Original commit 
301961 Mk/
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 ] Original commit 
301878 Mk/
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.

in the end for the sake of some ports relying on that.

PR:		169449
Discussed with:	bf
Tue, 26 Jun 2012
[ 13:54 sunpoet ] Original commit 
1.66 Mk/
1.731 Mk/
1.150 Mk/
- Revert accidental commit
[ 13:42 sunpoet ] Original commit 
1.65 Mk/
1.85 Mk/
1.730 Mk/
1.149 Mk/
- Add shared TLS description
Wed, 23 May 2012
[ 08:17 miwi ] Original commit 
1.36 Mk/
1.42 Mk/
1.14 Mk/
1.11 Mk/
1.75 Mk/
1.4 Mk/
1.64 Mk/
1.58 Mk/
1.174 Mk/
1.52 Mk/

(Only the first 10 of 33 ports in this commit are shown above. View all ports for this commit)
- 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 <> [1]
                dougb@ and Chris Rees <> [2]
                Garrett Cooper <> [3]
                "Bryan Drewery" <> [4]
Tested via:     phw
Sun, 29 Apr 2012
[ 12:20 gerald ] Original commit 
1.63 Mk/
Remove last reference to GCC 4.5 now that no port refers to it any more.
Sat, 12 Nov 2011
[ 22:03 gerald ] Original commit 
1.62 Mk/
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
Sun, 30 Oct 2011
[ 20:58 gerald ] Original commit 
1.61 Mk/
Fix mis-applied patch from revision 1.59 (moving the new code one
conditional up).

Discussed with: bf
[ 15:51 gerald ] Original commit 
1.60 Mk/
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 ] Original commit 
1.59 Mk/
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
Sat, 8 Oct 2011
[ 08:17 gerald ] Original commit 
1.58 Mk/
Fix the previous commit for the case where USE_FORTRAN is undefined.

Pointy hat to:  self, bf
[ 07:37 gerald ] Original commit 
1.57 Mk/
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
Mon, 19 Sep 2011
[ 00:40 gerald ] Original commit 
1.56 Mk/
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)
Sat, 10 Sep 2011
[ 12:10 gerald ] Original commit 
1.55 Mk/
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]
Sun, 4 Sep 2011
[ 16:56 gerald ] Original commit 
1.54 Mk/
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.
Sun, 31 Jul 2011
[ 22:40 gerald ] Original commit 
1.53 Mk/
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).
Tue, 19 Jul 2011
[ 21:16 gerald ] Original commit 
1.52 Mk/
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:
Wed, 4 May 2011
[ 22:33 flz ] Original commit 
1.109 Makefile
1.8 Mk/
1.51 Mk/
1.681 Mk/
1.78 Mk/
1.23 Mk/
Latest round of infrastructure changes.

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

PR:             ports/156575 [1],
                ports/139116 [2],
                ports/152498 [3],
                ports/155983 [4],
                ports/155510 [5],
                ports/156340 [6]
Submitted by:   Florent Thoumie <> [1],
                Sergey Skvortsov <> [2],
                Olli Hauer <> [3],
                Eitan Adler <> [4],
                Eitan Adler <> [5],
                Eitan Adler <> [6]
Tue, 1 Feb 2011
[ 01:41 gerald ] Original commit 
1.50 Mk/
lang/gcc44 and later depend on the devel/binutils port.  Leverage that
and USE_BINUTILS for every port we are building with this combo.  That
way all the tools in binutils may be used.

Suggested by:   bf
Feature safe:   yes
Sun, 17 Oct 2010
[ 11:24 gerald ] Original commit 
1.49 Mk/
Simplify the case of USE_FORTRAN=g77.  Update a comment.

Discussed with: bf
Tue, 28 Sep 2010
[ 02:48 gerald ] Original commit 
1.48 Mk/
In addition to CC and CXX now also set CPP with USE_GCC.  Add the output
of CPP to the test-gcc target.

Submitted by:   bf
Fri, 24 Sep 2010
[ 23:14 gerald ] Original commit 
1.47 Mk/
USE_FORTRAN=yes now implies lang/gcc45 up from lang/gcc44.

cad/salome and math/freemat needed some adjustments, apart from these
this looks like a far more easy upgrade than previous ones and according
to the upstream developers we do not even need to bump dependent ports
since GNU Fortran 4.4 and 4.5 are sufficiently compatible.

Tested by:      erwin (and pointyhat)
Sat, 4 Sep 2010
[ 17:08 gerald ] Original commit 
1.46 Mk/
Remove the transparent rewriting of USE_GCC=4.3+ to USE_GCC=4.4+.
Sat, 7 Aug 2010
[ 10:56 gerald ] Original commit 
1.35 Mk/
1.45 Mk/
Disconnect lang/gcc43, that is, USE_GCC=4.3 is not supported any longer.
Fri, 11 Jun 2010
[ 21:06 gerald ] Original commit 
1.44 Mk/
Extend and clarify the documentation for USE_GCC, making it explicit
that the form requesting a minimum version is preferred over the one
requesting just one version (as I had enhanced portlint to advise a
while ago).
Sun, 6 Jun 2010
[ 19:15 gerald ] Original commit 
1.43 Mk/
Tweak a conditional added in the previous commit that apparently causes
troubles in some cases.
[ 17:17 gerald ] Original commit 
1.42 Mk/
USE_GCC=4.3 is deprecated (and no port uses it anymore). USE_GCC=4.3+
is transparently rewritten to USE_GCC=4.4+ and lang/gcc43 will be
disconnected from the USE_GCC infrastructure soon.
Sun, 2 May 2010
[ 17:39 gerald ] Original commit 
1.41 Mk/
Add support for early GCC 4.6 snapshots (lang/gcc46) via USE_GCC=4.6
and USE_GCC=4.6+.  This version of GCC is in its very early development
stages and use thereof highly experimental.  Use at your own risk.
[ 14:44 gerald ] Original commit 
1.40 Mk/
Replace the use of GCC 4.3 in a comment/example by GCC 4.5 since the
former will be gone soon.
Sun, 14 Feb 2010
[ 22:36 gerald ] Original commit 
1.39 Mk/
Locate the GCC run-time libraries under ${LOCALBASE}, where the GCC
ports are installed/assumed, instead of ${PREFIX} where a dependent
port is installed.

Reported by:    Rob Farmer <>
Sat, 2 Jan 2010
[ 13:51 gerald ] Original commit 
1.38 Mk/
Split the logic around USE_GCC in two parts.  The first handles the
processing of USE_GCC directives, the second then takes a concrete
selection coming from the previous or the code handling USE_FORTRAN
via _USE_GCC.

The one user-visible change is that not just users of USE_FORTRAN,
but now also users of USE_GCC set an rpath via CFLAGS and LDFLAGS. [1]

PR:             129518, 142226 [1]
[ 12:05 gerald ] Original commit 
1.37 Mk/
Quote the output for BUILD_DEPENDS and RUN_DEPENDS in the test-gcc
target.  This is necessary to properly handle dependencies such as
[ 08:11 gerald ] Original commit 
1.36 Mk/
Add a run-time dependency for all uses of lang/gcc* except for gcc34
which is subsumbed by later versions.  This is needed for libstdc++
and other core run-time libraries.

PR:             129518, 142226
Sat, 10 Oct 2009
[ 11:45 gerald ] Original commit 
1.35 Mk/
Add support for USE_GCC=4.5 and USE_GCC=4.5+.  Improve the documentation
a bit.

Suggested by:   bsam
Sat, 26 Sep 2009
[ 01:02 gerald ] Original commit 
1.34 Mk/
Have CFLAGS and LDFLAGS set an -rpath to the lang/gcc44 library directory
when building with USE_FORTRAN=yes.  This makes us use
(and others) brought by this port as opposed to /usr/bin/
that comes with our system compiler which is based on an older version
of GCC 4.2.  Newer version of GCC run-time libraries with the same soname
are always backwards compatible.

Feature safe:   yes
Wed, 23 Sep 2009
[ 21:13 gerald ] Original commit 
1.33 Mk/
Also print LDFLAGS as part of the test-gcc target.  Print quotes around
CFLAGS and FFLAGS, too, to exactly see where we have whitespace.

Feature safe:   yes
Sat, 12 Sep 2009
[ 18:07 gerald ] Original commit 
1.32 Mk/
USE_FORTRAN=yes now implies lang/gcc44 up from lang/gcc43.  Remove one
explicit reference to the version number on the way.

Tested by:      pav (and pointyhat)
Thanks to:      pav, everyone who helped up fixing their ports
Sun, 12 Jul 2009
[ 22:35 gerald ] Original commit 
1.31 Mk/
Tweak some comments.  The two non-whitespace changes are a fix from
/lang/gcc43 to lang/gcc43 and removing to notes that might be seen
as indicative of GCC only being needed at build time.
Fri, 19 Jun 2009
[ 17:48 gerald ] Original commit 
1.30 Mk/
Remove support for USE_GCC=2.95 after lang/gcc295 has been failing to
build for what must be 9+ months and we have removed all dependencies
the last couple of months.
Sat, 28 Mar 2009
[ 23:57 gerald ] Original commit 
1.29 Mk/
Remove GCC 2.8 from the list of options for USE_GCC; the lang/gcc28
port has been removed a while ago and no port has USE_GCC=2.8 in use.
Sat, 7 Mar 2009
[ 19:17 gerald ] Original commit 
1.28 Mk/
Remove support for GCC 3.3.  No port in the tree uses this any longer,
and lang/gcc33 has been deprecated for a month.
Mon, 2 Feb 2009
[ 01:45 gerald ] Original commit 
1.27 Mk/
Set CC and CXX to match the choice of GNU Fortran compilers for C and
C++, too, to avoid subtle compatibility problems.

Diagnose the case where an unexpected value is provided for USE_FORTRAN.

Fix the OSVERSION for which lang/gcc34 should be used foor USE_FORTRAN=g77
according to our Porters Handbook.

Add RUN_DEPENDS to the output of the test-gcc target.

PR:             131114
Submitted by:
Sun, 18 Jan 2009
[ 03:10 gerald ] Original commit 
1.26 Mk/
Add support for USE_GCC=4.4+ and remove USE_GCC=4.1+ (which is not used
by any other port at this point).

Number of commits found XX: 125 (showing only 100 on this page)

1 | 2  »  

User Login
Create account

Servers and bandwidth provided by
New York Internet, iXsystems, and RootBSD

This site
What is FreshPorts?
About the authors
How big is it?
The latest upgrade!

Enter Keywords:

Latest Vulnerabilities
dnsmasqJan 20
goJan 19
moinmoinJan 18
ghostscript9-agpl-baseJan 17
gitlab-ceJan 14
nodeJan 14
node10Jan 14
node12Jan 14
node14Jan 14
wavpackJan 14
jenkinsJan 13
jenkins-ltsJan 13
phpmyfaqJan 12
sudoJan 11
py-cairosvgJan 10

12 vulnerabilities affecting 81 ports have been reported in the past 14 days

* - modified, not new

All vulnerabilities

Last updated:
2021-01-23 18:22:23

Deleted ports
Sanity Test Failures

NEW Graphs (Javascript)

Calculated hourly:
Port count 42144
Broken 84
Deprecated 204
Ignore 319
Forbidden 4
Restricted 139
Vulnerable 18
Expired 39
Set to expire 179
Interactive 0
new 24 hours 1
new 48 hours5
new 7 days42
new fortnight99
new month288

Servers and bandwidth provided by
New York Internet, iXsystems, and RootBSD
Valid HTML, CSS, and RSS.
Copyright © 2000-2021 Dan Langille. All rights reserved.