Log message:
*: Assume that the user has a C99-capable compiler.

A compiler that supports -std=c99 is required for
bootstrap, so it doesn't make sense to specify a c99
compiler everywhere in package makefiles.

At any rate, I would bet my entire life's savings that
this is a small fraction of the total number of packages
requiring c99.

Note that compilers that default to c89 but support c99
are still supported...

Log message:
gcc9: move admonition about PKGREVSION next to the entry (NFC)

(Fix my previous adjustment.)

Log message:
gcc*-libs: fix PKGREVISION values that got out of sync (again)

Log message:
gcc*: include missing header and unbreak build on Linux.

Log message:
gcc*: Disable FORTIFY on Linux only

Log message:
lang/gccX: switch from USE_LANGUAGES=c99 to USE_CC_FEATURES/FORCE_C_STD.

Log message:
*: recursive bump for Python 3.11 as new default

Log message:
lang/gcc*: USE_TOOLS+=sed, not sed:run.

As far as I can tell, gcc needs this at build-time, not at run-time.

https://mail-index.netbsd.org/tech-pkg/2023/06/02/msg027624.html

Log message:
lang/gcc*: Set CC_FOR_BUILD and CXX_FOR_BUILD if cross-compiling.

Verified gcc6 and gcc7 cross-compile on NetBSD, at least if the
gcc-fortran option is disabled.  gcc8 and gcc9 have trouble because
of python (why do these have a full dependency on python?); gcc10 and
gcc12 are missing gcc/config/mips/netbsd64.h; gcc12 and gcc13 have a
cross-compile bug with missing __LIBGCC_*__ macros -- but in any
case, setting CC_FOR_BUILD and CXX_FOR_BUILD is obviously necessary
for cross-compilation.  Conditional on USE_CROSS_COMPILE, so no harm
to native builds.

Log message:
gcc9: fix previous