kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/Mk/bsd.gcc.mk

164 lines
4.6 KiB
Makefile
Raw Normal View History

- 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
2012-05-23 10:17:49 +02:00
#-*- tab-width: 4; -*-
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
# ex:ts=4
#
# bsd.gcc.mk - Support for smarter USE_GCC usage.
#
# Created by: Edwin Groothuis <edwin@freebsd.org>
#
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
2012-12-22 22:35:35 +01:00
# To request the use of a current version of GCC, specify USE_GCC=yes in
# your port/system configuration. This is the preferred use of USE_GCC.
Refer to bsd.default-versions.mk for the canonical version of GCC; no longer duplicate version information related to that.
2014-03-16 01:45:55 +01:00
# It uses the canonical version of GCC defined in bsd.default-versions.mk.
Document USE_GCC=any. Reformat the description a bit and use newer versions of GCC for reference.
2013-11-10 21:29:52 +01:00
#
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).
2010-06-11 23:06:18 +02:00
# If your port needs a specific (minimum) version of GCC, you can easily
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
2012-12-22 22:35:35 +01:00
# specify that with a USE_GCC= statement. Unless absolutely necessary
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.
2018-06-02 10:03:59 +02:00
# do so by specifying USE_GCC=X+ which requests at least GCC version X.
# To request a specific version omit the trailing + sign.
Document USE_GCC=any. Reformat the description a bit and use newer versions of GCC for reference.
2013-11-10 21:29:52 +01:00
#
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
2021-01-30 16:15:01 +01:00
# Optionally comma-separated arguments follow the version specifier.
# Currently we support:
# build ... which adds GCC as a build dependency (BUILD_DEPENDS) only.
#
# If no arguments are specified, GCC is added as both a build dependency
# and a run time dependency.
#
#
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.
2010-06-06 19:17:04 +02:00
# Examples:
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
2012-12-22 22:35:35 +01:00
# USE_GCC= yes # port requires a current version of GCC
Refer to bsd.default-versions.mk for the canonical version of GCC; no longer duplicate version information related to that.
2014-03-16 01:45:55 +01:00
# # as defined in bsd.default-versions.mk.
Mk/bsd.gcc.mk: User newer versions in examples
2021-07-16 14:39:41 +02:00
# USE_GCC= 11+ # port requires GCC 11 or later.
# USE_GCC= 9 # port requires GCC 9.
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
2021-01-30 16:15:01 +01:00
# USE_GCC= yes:build # port requires a current version of GCC at
# # build time only.
Mk/bsd.gcc.mk: User newer versions in examples
2021-07-16 14:39:41 +02:00
# USE_GCC= 10:build # port requires GCC 10 at build time only.
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
2021-01-30 16:15:01 +01:00
# USE_GCC= 11+:build # port requires GCC 11 or later at build
# # time only.
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
#
# If you are wondering what your port exactly does, use "make test-gcc"
# to see some debugging.
- Transfer maintainership of this file to Gerald Pfeifer
2007-01-29 10:27:04 +01:00
GCC_Include_MAINTAINER= gerald@FreeBSD.org
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
Simplify a comment after r531883 | gerald | 2020-04-16 (which in turn simplified the structure of Mk/bsd.gcc.mk).
2020-06-20 23:57:57 +02:00
# All GCC versions supported by this framework.
#
Streamline two comments and remove debugging output we hardly need any longer (and will need even less shortly).
2020-03-12 10:03:04 +01:00
# When updating this, keep Mk/bsd.default-versions.mk in sync.
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.
2021-07-01 08:39:30 +02:00
GCCVERSIONS= 4.8 8 9 10 11 12
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
Refer to GCC 4.7 instead of GCC 4.5. Mark the part that should not see changes based on GCC changes more clearly.
2011-10-30 16:51:09 +01:00
# No configurable parts below this. ####################################
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
#
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
2021-01-30 16:15:01 +01:00
# Split arguments
.if defined(USE_GCC)
__USE_GCC:= ${USE_GCC:C/\:.*//}
_USE_GCC_ARGS:= ${USE_GCC:C/^[^\:]*(\:|\$)//:S/,/ /g}
USE_GCC= ${__USE_GCC}
.endif
.if ${_USE_GCC_ARGS:Mbuild}
_USE_GCC_ARGS:= ${_USE_GCC_ARGS:Nbuild}
.else
_USE_GCC_RUN_DEPENDS= yes
.endif
.if !empty(_USE_GCC_ARGS)
IGNORE= bad target specification in USE_GCC; only "build" is supported
.endif
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)
2012-10-07 21:33:19 +02:00
.if defined(USE_GCC) && !defined(FORCE_BASE_CC_FOR_TESTING)
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
2021-10-15 19:43:11 +02:00
# Handle USE_GCC=yes.
.if ${USE_GCC} == yes
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.
2020-04-03 23:46:40 +02:00
USE_GCC= ${GCC_DEFAULT}+
.endif
Provide the test-gcc target and at least key information there even if USE_GCC has not been specified. This is relevant for USE_FORTRAN, but should be useful in general.
2008-06-28 18:52:40 +02:00
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
2011-11-12 23:03:55 +01:00
# See if we can use a later version or exclusively the one specified.
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
_USE_GCC:= ${USE_GCC:S/+//}
.if ${USE_GCC} != ${_USE_GCC}
_GCC_ORLATER:= true
.endif
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.
2020-02-22 11:15:04 +01:00
# See whether we have the specific version requested installed already
# and save that into _GCC_FOUND. In parallel, check if USE_GCC refers
# to a valid version to begin with.
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
.for v in ${GCCVERSIONS}
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.
2020-04-17 00:25:20 +02:00
. if ${_USE_GCC} == ${v}
Merge two loops and initialize _GCC_FOUND${v} and check whether USE_GCC points to a valid version in parallel.
2013-03-29 12:26:14 +01:00
_GCCVERSION_OKAY= true
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.
2020-04-17 00:25:20 +02:00
. if exists(${LOCALBASE}/bin/gcc${v:S/.//})
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.
2020-02-22 11:15:04 +01:00
_GCC_FOUND:= ${_USE_GCC}
. endif
Merge two loops and initialize _GCC_FOUND${v} and check whether USE_GCC points to a valid version in parallel.
2013-03-29 12:26:14 +01:00
. endif
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
.endfor
Merge two loops and initialize _GCC_FOUND${v} and check whether USE_GCC points to a valid version in parallel.
2013-03-29 12:26:14 +01:00
.if !defined(_GCCVERSION_OKAY)
IGNORE= Unknown version of GCC specified (USE_GCC=${USE_GCC})
.endif
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
# If the GCC package defined in USE_GCC does not exist, but a later
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.
2020-02-22 11:15:04 +01:00
# version is allowed (for example 8+), go and use the default.
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
.if defined(_GCC_ORLATER)
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.
2020-02-22 11:15:04 +01:00
. if !defined(_GCC_FOUND) && ${_USE_GCC} < ${GCC_DEFAULT}
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.
2014-02-24 23:15:32 +01:00
_USE_GCC:= ${GCC_DEFAULT}
Fix mis-applied patch from revision 1.59 (moving the new code one conditional up). Discussed with: bf
2011-10-30 21:58:22 +01:00
. endif
.endif # defined(_GCC_ORLATER)
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
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.
2020-04-03 23:46:40 +02:00
# A concrete version has been selected. Set proper ports dependencies,
# CC, CXX, CPP, and flags.
V:= ${_USE_GCC:S/.//}
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).
2021-06-21 09:25:53 +02:00
. if ${V} == 12
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.
2020-04-26 16:20:35 +02:00
_GCC_PORT:= gcc${V}-devel
. else
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
2012-08-03 04:28:37 +02:00
_GCC_PORT:= gcc${V}
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.
2020-04-26 16:20:35 +02:00
. endif
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
CC:= gcc${V}
CXX:= g++${V}
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
2010-09-28 04:48:29 +02:00
CPP:= cpp${V}
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]
2012-08-03 23:23:04 +02:00
_GCC_RUNTIME:= ${LOCALBASE}/lib/gcc${V}
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.
2020-04-03 23:46:40 +02:00
. if ${PORTNAME} == gcc
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@
2018-12-29 16:38:30 +01:00
# We don't want the rpath stuff while building GCC itself
# so we do not set the FLAGS as done in the else part.
# When building a GCC, we want the target libraries to be used and not the
# host GCC libraries.
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.
2020-04-03 23:46:40 +02:00
. else
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]
2012-08-03 23:23:04 +02:00
CFLAGS+= -Wl,-rpath=${_GCC_RUNTIME}
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
2012-11-06 01:23:43 +01:00
CXXFLAGS+= -Wl,-rpath=${_GCC_RUNTIME}
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
2013-12-07 23:36:21 +01:00
LDFLAGS+= -Wl,-rpath=${_GCC_RUNTIME} -L${_GCC_RUNTIME}
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.
2020-04-03 23:46:40 +02:00
. endif
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
.undef V
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
2018-08-05 15:30:30 +02:00
# Now filter unsupported flags for CC and CXX.
CFLAGS:= ${CFLAGS:N-mretpoline}
CXXFLAGS:= ${CXXFLAGS:N-mretpoline}
Simplify the logic by removing a variable (_GCC_PORT_DEPENDS) and instead use two equivalent ones (depending on the circumstances).
2020-04-09 22:43:02 +02:00
.if defined(_GCC_PORT)
BUILD_DEPENDS+= ${CC}:lang/${_GCC_PORT}
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
2021-01-30 16:15:01 +01:00
. if defined(_USE_GCC_RUN_DEPENDS)
Simplify the logic by removing a variable (_GCC_PORT_DEPENDS) and instead use two equivalent ones (depending on the circumstances).
2020-04-09 22:43:02 +02:00
RUN_DEPENDS+= ${CC}:lang/${_GCC_PORT}
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
2021-01-30 16:15:01 +01:00
. endif
Simplify the logic by removing a variable (_GCC_PORT_DEPENDS) and instead use two equivalent ones (depending on the circumstances).
2020-04-09 22:43:02 +02:00
# GCC ports already depend on binutils; make sure whatever we build
# leverages this as well.
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
2011-02-01 02:41:19 +01:00
USE_BINUTILS= yes
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
.endif
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.
2020-04-03 23:46:40 +02:00
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)
2012-10-07 21:33:19 +02:00
.endif # defined(_USE_GCC) && !defined(FORCE_BASE_CC_FOR_TESTING)
Provide the test-gcc target and at least key information there even if USE_GCC has not been specified. This is relevant for USE_FORTRAN, but should be useful in general.
2008-06-28 18:52:40 +02:00
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
test-gcc:
@echo USE_GCC=${USE_GCC}
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]
2013-03-16 14:01:12 +01:00
.if defined(IGNORE)
@echo "IGNORE: ${IGNORE}"
.else
Provide the test-gcc target and at least key information there even if USE_GCC has not been specified. This is relevant for USE_FORTRAN, but should be useful in general.
2008-06-28 18:52:40 +02:00
.if defined(USE_GCC)
* Change bento to pointyhat names in comments. [1] * Document DISABLE_VULNERABILITIES variable. [2] * Add WWW: line for 'search' target. [3] * Speedup check-vulnerable invokation, if portaudit is installed. [4] * Run install-info for all .info files. [5] * Run add-plist-docs more strictly and prevent some situations with leftover files in the future. [6] * Introduce two new variables: MASTER_PORT and SLAVE_PORT. The results from these variables is only used as information for users. [7] * Honour OPTIONS if PACKAGE_BUILDING or BATCH are defined. [8] * Move all USE_GCC entries to new file - bsd.gcc.mk. 'test-gcc' target allows users to check gcc version if USE_GCC is used. Give maintainers opportunity to add '+' character to USE_GCC version for using specified and higher versions. [9] * Install startup scripts with the help of USE_RC_SUBR variable. [10] * Add three new targets: config-recursive, rmconfig-recursive and config-conditional. You can set or delete OPTIONS for all dependencies before every build. config-conditional target is used to skip configuring ports which have already been configured. [11] * Fix using of WANT_PGSQL_VER variable if postgresql is already installed. [12] PR: ports/75768 [1], ports/75728 [2], ports/76187 [3], ports/76191 [4], ports/76182 [5], ports/75379 [6], ports/75286 [7], ports/75727 [8], ports/76489 [9], ports/73691 ports/69217 [10], ports/76254 [11], ports/76988 [12] Submitted by: dinoex [1], edwin [2] [5] [6] [8] [9] [10], Marcus Grando <marcus@corp.grupos.com.br> [3], tobez and Valentin Nechayev <netch@netch.kiev.ua> [4], linimon [7], Florent Thoumie <flz@xbsd.org> [10], Chris Dillon <cdillon@wolves.k12.mo.us> [11], girgen [12]
2005-02-07 12:17:50 +01:00
.if defined(_GCC_ORLATER)
@echo Port can use later versions.
.else
@echo Port cannot use later versions.
.endif
* Split bsd.port.mk pre and post includes into 3 pieces instead of 2, to allow OPTIONS to be able to influence dependencies. This is still experimental [1] * Teach bsd.gcc.mk about gfortran [2] * Remove the outdated emulators/linux_base; the new default has been linux_base-fc4. This will allow the outdated port to be removed [3] * Add USE_FIREBIRD macros to bsd.database.mk [4] PR: 93687 [1], 93690 [2], 103184 [3], 103357 [4] Submitted by: shaun [1], Pedro F. Giffuni <giffunip at asme to org> [2], gerald [2], thierry [2], vd [3], skv [4]
2006-09-30 21:25:46 +02:00
@echo Using GCC version ${_USE_GCC}
Provide the test-gcc target and at least key information there even if USE_GCC has not been specified. This is relevant for USE_FORTRAN, but should be useful in general.
2008-06-28 18:52:40 +02:00
.endif
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.
2018-08-05 14:14:28 +02:00
@echo CC=${CC} - CXX=${CXX} - CPP=${CPP}
@echo CFLAGS=\"${CFLAGS}\"
@echo CXXFLAGS=\"${CXXFLAGS}\"
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
2009-09-23 23:13:07 +02:00
@echo LDFLAGS=\"${LDFLAGS}\"
Quote the output for BUILD_DEPENDS and RUN_DEPENDS in the test-gcc target. This is necessary to properly handle dependencies such as libtool>=2.2:${PORTSDIR}/devel/libtool22.
2010-01-02 13:05:30 +01:00
@echo "BUILD_DEPENDS=${BUILD_DEPENDS}"
@echo "RUN_DEPENDS=${RUN_DEPENDS}"
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]
2013-03-16 14:01:12 +01:00
.endif
Reference in a new issue Copy permalink