as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
`${foo.__}` should not expand to parent node
This was an experimental feature that was added after last stable
release. Disable it.
Fixes upstream issue #1116.
This brings in the following important commit on github:
Ensure fd 0, 1, 2 are never closed
Closing stdin, stdout, or stderr is extremely dangerous and
should never be done. If an attempt is made to do so redirect
the file descriptor to /dev/null. Similarly, if ksh is started
with one of those fd's closed open it on /dev/null before doing
anything else.
Resolving upstream issue #1117.
Notable fixes:
Fix `${+}` parameter expansion inside loops
`nv_getval()` function internally calls `nv_optimize()` and
optimizations outside `varsub()` function depend on it. Using
`nv_isnull()` instead of `nv_getval()` was causing broken behavior
with `${+}` parameter expansions inside loops.
Resolves: #70
Notable fixes are:
Sync all streams before restoring file descriptors
This was causing issues while truncating files. Sync all streams
before restoring file descriptors to avoid any similar issues in
future.
Simplify some ports where DragonFlyBSD no longer needs to be special-cased.
Submitted by: rene
Reviewed by: bapt, jbeich
Differential Revision: https://reviews.freebsd.org/D17724
Coverity Out-of-bounds read
This Coverity Scan issue appears to be a false positive.
This change is a reformulation of the code that attempts
to both clarify the behavior and suppress the false positive
error.
Coverity CID#316729
of installing ksh as ${LOCALBASE}/bin/ksh instead of as
${LOCALBASE}/bin/ksh93. If the KSH option is chosen, this port will
conflict with shells/pdksh. By default the binary that is installed is
ksh93 (conflicting with shells/ksh).
In the future, we might want to add a little ports infrastructure
allowing ports that need a ksh to depend on one of the various ksh or
ksh clones in ports.
