ksh supports multiple sources of heap memory. Completely disable the
use of sbrk() as a memory source in favor of mmap(). This allows
compilation on aarch64 (and presumably riscv64).
Approved by: cy
Differential Revision: https://reviews.freebsd.org/D37312
Commit b7f05445c0 has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.
There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.
The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.
Approved by: portmgr (tcberner)
Add an option to allow the ksh ports to avoid conflicting with each
other and to coexist. This allows people who wish to punish themselves
by tracking developent to still be able to fall back should upstream
cause regressions.
This also allows legacy ksh93 to coexist with the recently added
ksh93/ksh, which is not entirely compatible with legacy ksh. Applications
which require a legacy ksh compatible package should use the ksh93 port
installed using one of its options. This allows new and old to exist on
the same system.
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Approved by: portmgr (blanket)
63e9edcb6084d4b164439065e2d71f3e900ec3c7 resolves this issue.
Unfortunately it does not apply, requiring this port to be upated to
ksh93 well into ksh93-devel. Bringing ksh93 up to the ksh93-devel or
shy of it would negate the justification for ksh93's existence. It is
therefore recommended that people use ksh93-devel on architectures that
use GCC 9 or use GCC 8.
PR: 239644
Reported by: pkubaj@
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
yours truly).
The maintainer no longer wants to maintain ksh93 as his desire is to
maintain a backlevel port of ksh93 in order to build and support a
shared library for use by legacy applications, which is inconsistent
with the direction of the att/ast team on github. I will maintain the
port.
PR: 237332
PR: 238266
Approved by: maintiner (saper@saper.info)
2020.0.0-alpha1.
Following this commit will be an svn copy shells/ksh93-devel to
shells/ksh93, replacing the git tag with DISTVERSION 2020.0.0-alpha1.
PR: 237332
Approved by: maintainer timeout
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
The ksh93 build process requires the pre-GCC5 CPP newline behavior, which
the -P argument provides by disabling line markers. This enables ksh93
to be built by gcc5 and later.
Approved by: GCC blanket
PR: 216707 (related)
Turns out that env(1) knows how to parse a properly quoted string
using -S "string", it makes the double eval used for the fetch
command to be unnecessary.
This is because running:
eval "foo $(escape $bar)"
is silly when this works:
foo $bar
So remove escaping and quoting, and sillyness.
PR: 210198
Submitted by: mat
Exp-run by: antoine
Sponsored by: The FreeBSD Foundation, Absolight
Differential Revision: https://reviews.freebsd.org/D6779
