The BROKEN_SSL variable is already filled in the case the OPENSSL option
is checked. Those extra lines were left-over from a debugging session.
No need to MFH this commit, the MFH of the initial change took care of
not adding them in the first place.
With some patching [1], Erlang 19.x supports OpenSSL 1.1.x (lang/erlang,
lang/erlang-runtime19).
However, previous versions are now marked as broken with OpenSSL 1.1.x.
PR: 225898
Submitted by: brnrd [1]
Obtained from: Upstream
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
- Convert all ports to options helpers
- Add MANPAGES option to lang/erlang
- Remove HTML and PDF documentation from lang/erlang (went into erlang-doc)
- Remove APP_UPGRADE code because of the doc split
- Reduce diffs between all Makefiles
- Enable dirty schedulers by default on version 20
- Non-SMP beam is deprecated on version 20, so enable SMP unconditionally
(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.
Pkg always wants to install compat10x-amd64 when using the port's default RPATH.
The same fix can be found in Suse, and in Erlang packages from RabbitMQ.
Noticed by: lwhsu, bapt
All applications in the ports tree works correctly with unicode version of wxGTK
Newer version of wxGTK are unicode only (3.0+)
Note that now WX_UNICODE macro is noop
Always rely on unixODBC each time a port is looking for libodbc.so
Remove odbc compat from libiodbc
This allows to install both kde and gnome at the same time
While here:
- Convert libiodbc to USES=libtool
- Convert a bunch of libiodbc dependencies to USES=libtool
- Chase libiodbc.so shlib change
- Stagify some ports
- Convert some ports to USES=pgsql
Discussed with: rakuco (kde)
With hat: portmgr
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
is enabled. It was added in r300328 to fix compilation with clang but
testing has shown it is no longer necessary.
PR: ports/180017
Tested by: Stefan Grundmann <sg2342@googlemail.com>
Right now this is a noop in the former case and a noop in the latter
case unless lang/gcc44 has been installed explicitly.
This puts a bit more emphasis on standardizing on a canonical version
"current" GCC and makes it easier to update that canonical version
by changing the default in Mk/bsd.gcc.mk and updating the lang/gcc port.
That is, USE_GCC=yes means "use a decent/modern version of GCC" without
having to worry about details.
Approved by: portmgr (bdrewery)
