Re: First go at adding GCC_VERSIONS_ACCEPTED support

[David Sainty <david.sainty%gmail.com@localhost>]

On 3 October 2015 at 00:57, Greg Troxel <gdt%ir.bbn.com@localhost> wrote:

David Sainty <david.sainty%gmail.com@localhost> writes:

> On 02/10/15 11:45, Greg Troxel wrote:
> GCC_REQD
>
> A list of values specifying the minimum version of the GNU Compiler
> Collection that is required to build this package.  The list is
> constructed from version numbers appended by this package and by any
> included buildlink3.mk files.  Each package or buildlink3.mk file will
> generally append at most a single version number to GCC_REQD; forming
> a list of version numbers of which the maximum version is the
> definitive one.

Can we say "each package sets exactly one"?  If it's "the mininum", more
doesn't make sense.

Again, just trying to improve the existing documentation, how about:

GCC_REQD

A list of values specifying the minimum version of the GNU Compiler Collection that is required to build this package.  The list is constructed from version numbers appended by this package and by any included buildlink3.mk files.  Each package or buildlink3.mk file will (effectively) append at most a single version number to GCC_REQD.  The end result is a list of version numbers, which is then reduced down to the single, maximum version as the definitive required version.  Any version numbers in the list that are less than the maximum are subsequently ignored, playing no further part in selecting which compiler to use.

Setting this variable doesn't change the compiler that is used for building packages. See ONLY_FOR_COMPILER for that purpose.

This variable can also be set by the user when USE_PKGSRC_GCC is in effect to ensure that a specific compiler is used for packages which do not specify a higher version.