Despite what Solar Designer had said earlier, community enhancements
were not offered as separate patch, so the top comment about JUMBO
option still stands.
Because supported SIMD features are detected during configure, force
SSE2 for x86 packages as reasonable default which most modern CPUs
should support these days. Ideally we should probably do several build
rounds and produce binaries targeting different SIMD features (e.g.
like Arch Linux is doing this), but that's the task for another day.
Actualize the lists of binaries and symlinks (some programs had become
standalone, others had been converted to scripts offered as extras).
Drop BROKEN_mips64: it was added in r425682 five years ago for a
different version, since then similar breakage for aarch64 had been
fixed, and looking at the configure script, mips64 should be supported
(even if it's really not, that particular error message is no longer
accurate per grepping the sources).
Adjust LICENSE (GPLv2 or later) and fix the build with OpenCL support.
PR: 247229, 254922
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
- Drop the note that we prefer -jumbo (community-enhanced) versions
instead of vanilla JtR releases and accompanying PORTSCOUT knob,
add a nota bene to handle this with next JtR version update
- Remove broken mirror (gd.tuwien.ac.at) from the MASTER_SITES
- Remove BROKEN_SSL knob, it should build fine after recent changes
- Shorten BROKEN_$arch messages and fix a minor typo there
- While Solar Designer recommends to pass JOHN_SYSTEMWIDE_HOME and
JOHN_SYSTEMWIDE_EXEC overrides via command line, in practice it
is easier and cleaner (avoids plenty of those ``warning: missing
terminating '"' character [-Winvalid-pp-token]'' messages during
configure stage) to patch `params.h' file in place, so do it
- For JOHN_SYSTEMWIDE=1, pass it via environment (as CFLAGS_EXTRA)
instead of appending to global CFLAGS value
- GC `pfx2john' symlink (should've been part of r494924)
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
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, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
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, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
expanding them to cover newly added files, and augment OPENSSL_NO_SHA0
patch to avoid linking error
- Restore `-flax-vector-conversions' option required on pre-Clang systems
that was erroneously removed in r425958
PR: 214459
- Remove no longer needed build-related logic since they moved to GNU
autotools' based build
- Disable OPENMP option for the moment; it will be reintroduced with
others (e.g. OpenCL) in a separate commit
- Add upstream patch to fix the build on non-x86 architectures [2]
- Do not define _POSIX_SOURCE when compiling wordlist.c: this results
in broken JtR binary at least on i386
- Define JOHN_SYSTEMWIDE_EXEC for the future when we start to provide
fall-back binaries
- Stop moving john.conf to /etc. We're not doing it for other *.conf
files anyway (the include files); JtR is smart enough to locate its
configuration files properly when built in system-wide mode [1]
- Install full set of documentation files included with -jumbo
- Remove `xtract' symlink which hasn't been part of JtR for more than
a decade; install more useful symlinks (unafs, unique, other un* and
*2john) that were added in -jumbo instead
- Previously *.pl, *.rb, and *.py scripts were installed into DATADIR;
Alexander wanted to see them along with the documentation, but that
goes a bit too far; put them in ${DATADIR}/extra for the time being
PR: 197172 [1]
Obtained from: http://www.openwall.com/lists/john-dev/2014/12/18/21 [2]
The following 4 ports will not build correctly if certain variables
are not defined as "freebsd". Defining them as "${OPSYS:tl}" caused
breakage on DragonFly for various reasons. Harding the variables are
a no-op for FreeBSD but fixes the ports on DragonFly.
* games/ioquake3
* graphics/opendx
* science/cdf
* security/john
approved by: portmgr (bapt)
Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)
bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore
Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier
With hat: portmgr
- Add an OPTION to build with OpenMP support (disabled by default)
- Adjust `pre-build' target message to mention OpenMP support (with/without)
- Fix overly aggressive CFLAGS patching via REINPLACE_CMD
- Remove unneeded global modifiers from sed(1) expressions and kill one
superfluous empty line while I am here
