lang/gcc48: Remove expired port

2024-05-01 lang/gcc48: Unsupported by upstream since 2015. Use GCC 10 or newer
instead.

lang/gcc48: Moved man to share/man

Approved by:    portmgr (blanket)

lang/gcc48: Remove USES=makeinfo

- Distfile ships with info files pregenerated and no need to regenerate
  these files
- Remove patches to modify the changes in the texi file which were
  required for the texinfo in the base

lang/gcc48: try to unbreak the port's build on recent -CURRENT

Pacify system compiler which is used during the initial bootstrap
and got overly strict with the latest update.

Reported by:		pkg-fallout
Discussed with:		jhb
Differential Revision:	https://reviews.freebsd.org/D40941

*: Bump PORTREVISIONs for math/mpc update to 1.3.1

lang/gcc48: Set EXPIRATION_DATE

Commit 2c8ea965a6490057e4d4bb3ee5b46045352f55f0 has set an expiration
date for sysutils/uefi-edk2-bhyve-csm, which is the last port dependent
on lang/gcc48 with default options.

Hence, finally set an expiration date to the unsupported upstream
lang/gcc48 port. Expiration date is set one month after
the expiration of sysutils/uefi-edk2-bhyve-csm.

PR:		269646

Remove WWW lines that have been moved into Makefiles

Approved by:	portmgr (implicit)

Move more WWW entries from pkg-descr files into Makefiles

The WWW: lines in the pkg-descr files of these ports where not at the
end of those files and have been missed in prior conversion runs.

Approved by:	portmgr (implicit)

lang: remove 'Created by' lines

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

  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Akinori MUSHA aka knu <knu@idaemons.org>
  *  Alex Dupre <ale@FreeBSD.org>
  *  Alexey Dokuchaev <danfe@FreeBSD.org>
  *  Alonso Cardenas Marquez <acm@FreeBSD.org>
  *  Andreas Klemm <andreas@klemm.gtn.com>
  *  Andrew Pantyukhin <infofarmer@FreeBSD.org>
  *  Andrey Zakhvatov
  *  Anton Berezin <tobez@FreeBSD.org>
  *  Anton Berezin <tobez@tobez.org>

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

Resign as maintainer of this port of GCC 4.8 which has been unsupported
upstream since 2015 and marked deprecated for three years now.

sysutils/memtest86+ and sysutils/uefi-edk2-bhyve are two remaining users
in the entire ports tree which hopefully will be converted at one point.

On the way refer to GCC 10 instead of GCC 9 for a recommended update.

And move the USES block earlier in the Makefile as newer GCC ports do
to honor our coding standards (and pet portlint).

Also remove -march=haswell from CFLAGS and CXXFLAGS since GCC 4.8
does not specifically support Intel Haswell.

With that we should have covered all attempts people reported of
setting CPUTYPE that GCC 4.8 does not support.

PR:		218819

Backport r553560 | gerald | 2020-10-28 from lang/gcc7:

  Our only [two consumers] in the tree [do] not require Fortran nor
  Objective-C, so do not build those front ends and libraries any longer.

  Also remove the BOOTSTRAP option, which has been the default all along,
  and bootstrap unconditionally, further simplifying this port.

Remove -march=ivybridge from CFLAGS and CXXFLAGS if present since this
version of GCC does not support the Intel Ivy Bridge architecture.

PR:		244654

Remove -march=westmere from CFLAGS and CXXFLAGS if present since this
old version of GCC (end of life for more than five years) does not yet
support the Intel Westmere architecture. [1]

This avoids breaking users who set a global CPUTYPE to westmere.

While here, backport r469788 from lang/gcc6: [2]

  Filter the -mretpoline command-line option, which is understood by
  recent versions of clang (and used in the context of the Spectre
  security issues), but not GCC (which uses different options for the
  same) from CFLAGS and CXXFLAGS.

  This avoids the build of this port via bootstrap, which is the default
  and leverages both the system compiler (clang in most cases) plus a just
  built version GCC, to fail due to the latter not knowing -mretpoline.

PR:		250263 [1], 228205 [2]
Reported by:	Patrick McMunn <doctorwhoguy@gmail.com> [1]
Submitted by:   rozhuk.im@gmail.com [2]

Remove three arm-specific local patches since r524029 restricted this
port to amd64 and i386.  This complements r539330 which only covered
the Makefile.

Since r524029 | gerald | 2020-01-25 this port has been restricted to
amd64 and i386 and is only still in our tree for the sake of two other
ports (specific to those two architectures).

Remove remaining traces of support for other architectures.

This change should not have any impact on anything installed or packaged.

This port, lang/gcc48, is only still alive due to dependencies by
sysutils/uefi-edk2-bhyve and sysutils/memtest86+.  Its successors
lang/gcc49 and lang/gcc5 have left the tree already, and lang/gcc6
is scheduled for removal soon.

Thus at least restrict to i386 and amd64, the only two platforms
supported by those two dependant ports.

Now that GCC 9 is the canonical version in the Ports Collection,
recommend that (instead of GCC 9) in the deprecation notes of ports
for old versions of GCC.

lang/gcc*: Hide pkg-message during upgrades

PR:		239419
Approved by:	gerald (maintainer)

Recommend the use of GCC 8 (instead of GCC 7 until now) to replace
these older versions of GCC - GCC 4.8, GCC 5, and GCC 6 - which have
been end-of-lifed upstream many moons ago.  GCC 8 has been the default
version of GCC in the Ports Collection for a while and as such proven
itself, plus of all versions it is most likely to be present/used.

No functional change, just updated advice to our users.

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

Recommend the use of GCC 7 or later over this port, since that is now
the default version of GCC for the Ports Collection.

After an include, PLIST_SUB must be appended to, not overwritten.

If it is overwritten, many values will be clobbered, and
pain will ensue.

PR:		230864
Submitted by:	mat
exp-runs by:	antoine

Simplify the setting of CFLAGS where /g is not necessary when substituting
a Makefile variable (since this takes place for every word in the variable,
not just once).

Run "/usr/sbin/service ldconfig restart" for USE_LDCONFIG instead of
"ldconfig -m <path>" so the order of ldconfig search directories after
package installation is the same as after a reboot.  The original command
simply appends the path to the list of directories while the ldconfig rc.d
script uses "sort -u".

Bump lang/gcc* which are known to install libraries with exactly the same
name so the library loaded at runtime depends on the order of the search
directories.

PR:		228046
Approved by:	portmgr (antoine)

Simplify MASTER_SITES in all GCC-ports related to end-of-lifed releases
(gcc47, gcc48, gcc49, and gcc5), taking advantage of the default for GCC
releases provided by MASTER_SITES_ABBREVS.

Reported by:	portlint

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

Fix builds of lang/gcc{48,49,5} with clang 6.0.0

Since clang++ 6.0.0 now defaults to -std=gnu++14 (similar to g++ 6 and
higher), building gcc48, gcc49 or gcc5 produce quite a number of
"invalid suffix on literal; C++11 requires a space between literal and
identifier" errors.  This is because in many places, double quotes are
directly followed by printf helper macros like HOST_WIDE_INT_PRINT.

In gcc 6 and later, spaces were added between the double quotes and the
macros, to fix this issue, but for earlier versions, use a combination
of find, grep and sed to add them mechanically throughout the respective
source trees.

In addition, gcc5 needs a regular patch to fix an incorrect call to
error(), which should have been error_at().  (This was a mismerge by
upstream.)

Approved by:	gerald (maintainer)
PR:		224927
MFH:		2018Q1

Backport the change to ensure what we install is stripped (i.e., debug
info is removed) from lang/gcc7 to lang/gcc47, lang/gcc48 and lang/gcc49.

(For more background see revisions 454177 and 454422.)

Reported by:	Ports QA Framework, miwi, sobomax
Discussed with:	tijl, miwi
Differential Revision:	https://reviews.freebsd.org/D10357

Given that GCC 5 has gone end-of-life now, recommend GCC 6 or later
instead of GCC 5 or later in the deprecation messages for lang/gcc46
to lang/gcc49.

Add deprecation notes for lang/gcc47, lang/gcc48, and lang/gcc49,
but no expiration date at this point (since at least the latter two
still have users in the ports tree and sparc64 relies on the latter).

PR:		222373
Submitted by:	Yasuhiro KIMURA <yasu@utahime.org>

Backport a number of changes from lang/gcc5 and lang/gcc49:

 - Move ONLY_FOR_ARCHS into the right position of the Makefile.

 - Omit a comment describing GCC_VERSION and SUFFIX.

 - Do not quote constant strings compared with ${ARCH}. [1]

 - Last, but not least the only functional change (and an important one):
   Remove headers being created by GCC's fixincludes machinery from
   the installation / packaging to avoid breakage when FreeBSD's headers
   are changing afterwards. [2]

PR:		221905 [1], 222233 [2]
Submitted by:	linimon [1]

Remove workarounds for PR 219274 that bapt@ had put in place in 2014
from the end-of-life lang/gcc4* ports.

PR:		219274

Adjust WWW reference in pkg-descr to https and avoid a trailing slash
for all lang/gcc4* ports.

Update print/texinfo to 6.3

Changes:	http://savannah.gnu.org/forum/forum.php?forum_id=8679
Differential Revision:	https://reviews.freebsd.org/D
PR:		218972
Exp-run by:	antoine

Remove files/patch-unwind-ia64.h which has been obsolete for a while
since ONLY_FOR_ARCHS does not include ia64.

Streamline the setting of INFO.

Now that this port does not feature support for Java/GCJ any longer,
we can simplify files/patch-arm-support accordingly.

Remove Java support (both in terms of the JAVA option and everything
associated with it as well as java from CATEGORIES) from this port.

Technically GCC 4.8 only went end-of-life upstream in June 2015, alas
GCC 4.9 and GCC 5 are well established by now and also provide support
for Java (GCJ/libgcj), and this change simplifies this port significantly
and speeds up the build.

In addition to the expected changes to Makefile, pkg-plist, and pkg-descr,
this also removes files/java-patch-hier.

- Fix shebang

Approved by:	gerald (maintainer via mail)

Replace the sole use of DISTVERSION (in MASTER_SITES) by PORTVERSION.

Inspired by:	mat

No longer define CPE_VERSION for ports tracking releases of GCC since
there the default of PORTREVISION is just fine.

Remove traces of armv6hf which no longer exists as an arch. [1]

Remove redundant definition of DISTVERSION and simplify GCC_VERSION.

Reported by:	andreast [1]

The output of tools like awk, date, sort, tr,... depends on the current
locale set by the user.  Add LANG=C and LC_ALL=C at the beginning of
bsd.port.mk and export them so all commands are executed with the C locale.
LC_ALL=C overrides all other LC_* variables.  LANG is used by setlocale(3)
as default value for LC_* variables, so normally it isn't used when LC_ALL
is set, but there's code out there that looks at LANG directly so it's safer
to set it as well.  The only commands not captured by this are !=
assignments before any inclusion of bsd.port.*mk.

Introduce USE_LOCALE=<locale> that adds LANG=<locale> and LC_ALL=<locale> to
CONFIGURE_ENV and MAKE_ENV so upstream build systems can be executed with a
different locale (e.g. USE_LOCALE=en_US.UTF-8).

PR:		215882
Exp-run by:	antoine
Approved by:	portmgr (antoine)

Move all ARM-specific bits we used to have in lang/gcc until r426565
(where I updated that port from GCC 4.8.5 to 4.9.4) to lang/gcc48.

Apart from these improvements these two ports used to be more or less
aligned, and not syncing them fully earlier looks like an omission.

Reported by:	linimon

Move the conflict with lang/gcc from lang/gcc48 to lang/gcc49 now that
we have updated lang/gcc to the GCC 4.9 series.  (The direction from
lang/gcc49 to the respective port already has been addressed.)

PR:		196712

${RM} already has -f.

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

Remove OPTIONS_DEFAULT_powerpc64=BOOTSTRAP which is redundant with
OPTIONS_DEFAULT.

Default powerpc64 to bootstrapping (option BOOTSTRAP) since otherwise
GCC can be mis-built, leading to an internal compiler error building
libgcc/libgcov.c, at least on FreeBSD 11.

Adjust OPTIONS_DEFINE_powerpc64 and OPTIONS_DEFAULT_powerpc64
incrementally (with +=) to avoid overwriting settings defined
at the top of the Makefile (or child ports). [1]

Submitted by:	swills [1]
Reported by:	swills

Pet portlint in terms of patch file format.

GCC uses an AWK script to generate source code that helps process
command-line options.  According to POSIX, string comparisons (and
hence sorting) are to be performed based on the locale's collating
order.  Alas GNU AWK only does so in POSIX mode, whereas starting
with FreeBSD 11 we do so by default, running into a bug (or false
assumption) with that script used by GCC.

Setting MAKE_ARGS such that AWK is always invoked in the C locale
works around this bug.

PR:		210122, 211742
Submitted by:	jkim

Apply the following to all common GCC ports based on end-of-life versions
of GCC including lang/gcc:

Only override CONFIGURE_TARGET for amd64 which is x86-64/x86_64 for the
rest of the world including GNU and GCC.  For all other architectures
it already defaults to the value we were setting.

Make MULTILIB_DESC consistent and more logical also for the lang/gcc
and lang/gcc48 ports, now in line across all lang/gcc* ports.

lang/gcc*: convert to CONFIGURE_OUTSOURCE

PR:		208294, 208309
Exp-run by:	antoine
Approved by:	gerald (maintainer)
Differential Revision:	https://reviews.freebsd.org/D4157

Remove ${PORTSDIR}/ from dependencies, categories h, i, j, k, and l.

With hat:	portmgr
Sponsored by:	Absolight

Add a MULTILIB option to gcc{,48,49,5} for powerpc64

This change is the same as r400632, which updated gcc[56]-devel, but now
for gcc{,48,49,5}.  This change is the second attempt at doing this: the
first attempt went in r401072 and was reverted in r401074 because the diff
was bogus and enabled the new MULTILIB option under all platforms instead
of just powerpc64.

This fixes the build of gcc{,48,49,5} under powerpc64 when the system
is built without the lib32 libraries.

More in detail:

If the system is built with lib32 support (WITH_LIB32, which is the default),
building gcc from ports results in a compiler that can target both 64-bit and

Revert r401072.

I'm not sure what happened exactly but I think I committed the change from
the wrong client.  The applied change enabled the MULTILIB option for all
architectures and not only powerpc64.  Let's just revert the commit and do
it properly from scratch; other things might be wrong so I wanna take a
closer look, and it's best to just revert quickly.

Add a MULTILIB option to gcc{,48,49,5} for powerpc64

This change is the same as r400632, which updated gcc[56]-devel, but now
for gcc{,48,49,5}.  Waited a week to ensure the change caused nothing to go
horribly wrong but this change is very low risk because it only affects
powerpc64.

This fixes the build of gcc{,48,49,5} under powerpc64 when the system
is built without the lib32 libraries.

More in detail:

If the system is built with lib32 support (WITH_LIB32, which is the default),
building gcc from ports results in a compiler that can target both 64-bit and
32-bit binaries on powerpc64.  However, when lib32 support is disabled
(WITHOUT_LIB32), gcc should only be built with 64-bit support or otherwise
the build fails.

To fix this, explicitly disable 32-bit support when /usr/lib32 is not present
and add a MULTILIB option (which is only defined for powerpc64 when 32-bit
support is possible and defaults to yes to preserve the current behavior) to
allow the user to explicitly control this feature.

Approved by:    gerald (maintainer), bdrewery (mentor), andreast
Differential Revision:  https://reviews.freebsd.org/D3952

Remove deprecated @exec/@unexec from ports using ccache-update-links

Remove UNIQUENAME and LATEST_LINK.

UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.

Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.

Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)

Reviewed by:	antoine, bapt
Exp-run by:	antoine
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D3336

Update to the GCC 4.8.5 release which concludes the GCC 4.8 release
branch -- no more releases nor snapshots nor even commits on this
branch are to be expected.

Update to the 20150611 snapshot of GCC 4.8.5.

Update to the 20150521 snapshot of GCC 4.8.5.

Remove the libgomp performance patches again.  Too many problem
reports by users.

Update to the 20150423 snapshot of GCC 4.8.5.

Merge MASTER_SITES and MASTER_SITE_SUBDIR into just the former. [1]

Suggested by:	mat [1]

Implement the FreeBSD specific pieces for thread affinity for OpenMP.

Upstream gcc 4.8 doesn't have support for this - it'll create threads,
but it won't do any of the thread affinity stuff for FreeBSD.

This allows for OMP_PROC_BIND=true to bind threads to their initial
CPUs, leading to some pretty drastic improvements in performance
for certain NUMA workloads.

Approved by:	gerald
Sponsored by:	Norse Corp, Inc.

Update to the 20150402 snapshot of GCC 4.8.5.

lang/gcc(46,47,48,49,5): Use OPTIONS_EXCLUDE_DragonFly to block JAVA

The JAVA frontend doesn't build on DragonFly on any release.  The new
OPTIONS_EXCLUDE_${OPSYS} feature is a nice way to avoid the use of
Makefile.DragonFly (most are in dports, but one is in lang/gcc5).

The recent addition of CXXFLAGS to lang/gcc5 prevents Makefile.DragonFly
on lang/gcc5 from being removed outright.  There are a couple of options
available to allow its removal, but I'll need to discuss with Gerald.

Approved by:	DragonFly blanket

Fix UNIQUENAME not being unique after recent PORTNAME shuffle.

This was causing the gcc packages to be generated with a
/usr/local/libdata/ldconfig/gcc file. All were conflicting. Bump
PORTREVISION to fix packages built during this time.

With hat:	portmgr
Reported by:	sunpoet

Add CONFLICTS with lang/gcc which is also GCC 4.8-based right now.

Add CPE information. [1]

Use PKGNAMESUFFIX so that PORTNAME falls back to plain gcc and we
can avoid setting DISTNAME and CPE_PRODUCT. [2]

PR:		198260 [1]
Submitted by:	shun.fbsd.pr@dropcut.net [1]
Suggested by:	mat [2]

Update to the 20150212 snapshot of GCC 4.8.5.

Update to the 20150129 snapshot of GCC 4.8.5.

Update to the 20150122 snapshot of GCC 4.8.5.

Update to the 20150108 snapshot of GCC 4.8.5.  This is a bit past
the GCC 4.8.4 release that the lang/gcc port is at, and likely will
lead to the last release on this branch.

When building the gcc ports using a full bootstrap, tell the configure
script to assume the BUILD_CONFIG is set to bootstrap-debug, instead of
letting it auto-detect.

With clang 3.5.0 this auto-detection can fail, due to a discrepancy [1]
[2] in its debug information, when objects are produced with and without
-g.  When the auto-detection fails, gcc will compare objects with full
debug information during the stage comparisons, and this sometimes
causes those stage comparisons to fail unexpectedly.

[1]
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20141222/250134.html
[2] http://llvm.org/PR22046

Approved by:	gerald (maintainer)

Update to the 20141218 snapshot of GCC 4.8.4.

Update to the 20141120 snapshot of GCC 4.8.4.

Update to the 20141106 snapshot of GCC 4.8.4.

Update to the 20141030 snapshot of GCC 4.8.4.

Update to the 20141023 snapshot of GCC 4.8.4.

Update to the 20141016 snapshot of GCC 4.8.4.

Remove all traces of @dirrm from the dynamically generated part of
pkg-plist.

Update to the 20141009 snapshot of GCC 4.8.4.

Update to the 20141002 snapshot of GCC 4.8.4.

Remove all instances of @dirrm from pkg-plist.

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

Reported by:	peter

Update to the 20140918 snapshot of GCC 4.8.4.

Update to the 20140911 snapshot of GCC 4.8.4.

Add USES=libtool

Update to the 20140904 snapshot of GCC 4.8.4.

Update to the 20140828 snapshot of GCC 4.8.4.

Update to the 20140807 snapshot of GCC 4.8.4.

Update to the 20140724 snapshot of GCC 4.8.4.

Update to the 20140710 snapshot of GCC 4.8.4.

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

Update to the 20140626 snapshot of GCC 4.8.4.

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 20140619 snapshot of GCC 4.8.4

Update to the 20140605 snapshot of GCC 4.8.4.

Add support for "-fstack-protector-strong".  This extends the
WITH_SSP_PORTS Makefile option in FreeBSD which adds "-fstack-protector"
and "-fstack-protector-all" command-line options that add extra code to
check for buffer overflows to ports built that way, cf.
https://gcc.gnu.org/onlinedocs/gcc-4.8.3/gcc/Optimize-Options.html

While this was a good first step, those switches offer too little
protection or too much overhead and so Google contributed a balanced
"-fstack-protector-strong". [1]

PR:		186852 [1]
Submitted by:	software-freebsd@interfasys.ch [1]

Update to the 20140522 snapshot of GCC 4.8.4 which is pretty much the
GCC 4.8.3 release.