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
Release announcement:
https://blog.qt.io/blog/2019/02/01/qt-5-12-1-released/
Changelog:
https://wiki.qt.io/Qt_5.12.1_Change_Files
- A change was required to qt-dist.mk to always pass LOCALBASE to qmake,
as Qt5 has been installed to a prefix for some time now, there should
not be any harm in that, with respect to it picking up installed versions
of itself during build.
PR: 235622
Exp-run by: antoine
a symbol matches multiple clauses the last one takes precedence. If the
catch-all is last it captures everything. In the case of Qt5 libraries
this caused all symbols to have a Qt_5 label while some should have
Qt_5_PRIVATE_API. This only affects lld because GNU ld always gives the
catch-all lowest priority.
Older versions of Qt5Webengine exported some memory allocation symbols from
the bundled Chromium. Version 5.9 stopped exporting these [1] but the
symbols were kept as weak wrappers for the standard allocation functions to
maintain binary compatibility. [2][3] The problem is that the call to the
standard function in these weak wrappers is only resolved to the standard
function if there's a call to this standard function in other parts of
Qt5Webengine, because only then is there a non-weak symbol that takes
precedence over the weak one. If there's no such non-weak symbol the call
in the weak wrapper resolves to the weak wrapper itself creating an infinite
call loop that overflows the stack and causes a crash. Some of the
allocation functions are variants of C++ new and delete and it probably
depends on the compiler whether these variants are used in other parts of
Qt5Webengine.
Remove the weak wrappers (make them Linux specific). This isn't binary
compatible but we are already breaking that with the changes to the symbol
versions.
[1] 5c2cbfccf9
[2] 2ed5054e3a
[3] 009f5ebb4b
Bump all ports that depend on Qt5.
PR: 234070
Exp-run by: antoine
Approved by: kde (adridg)
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
While here, chase some KDE4 ports and functionality, these are scheduled for
removal on 2018-12-31. Change the default option/flavor to QT5 where applicable
or use alternative toolkits like GTK.
Submitted by: tcberner
Reviewed by: adridg, jhale, rene, tcberner
Approved by: portmgr (implicit, flavor hook)
Differential Revision: https://reviews.freebsd.org/D17741
From now on, ports that depend on Qt4 will have to set
USES= qt:4
USE_QT= foo bar
ports depending on Qt5 will use
USES= qt:5
USE_QT= foo bar
PR: 229225
Exp-run by: antoine
Reviewed by: mat
Approved by: portmgr (antoine)
Differential Revision: →https://reviews.freebsd.org/D15540
As at the moment QT_BINDIR and QT_LIBDIR are 'bin' respectively 'lib' depending
on the Qt version these subs ended up at many wrong places in plists.
So only export it if QT_DIST is set.
PR: 210227
Reviewed by: mat, rakuco
Approved by: portmgr (mat), rakuco (mentor)
Differential Revision: https://reviews.freebsd.org/D8378
Release notes:
- https://community.kde.org/Phonon/Releases/Core/4.9.0
- https://community.kde.org/Phonon/Releases/GStreamer/4.9.0
- https://community.kde.org/Phonon/Releases/VLC/0.9.0
This release fixes the build with the upcoming Qt 5.6, which was failing like
this:
/usr/bin/c++ -O2 -pipe -fstack-protector -fno-strict-aliasing -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -Woverloaded-virtual -fno-common -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -Wno-return-type-c-linkage CMakeFiles/cmTC_08ed6.dir/check_qt_visibility.cpp.o -o cmTC_08ed6
CMakeFiles/cmTC_08ed6.dir/check_qt_visibility.cpp.o:(.qtversion[qt_version_tag]+0x0): undefined reference to `qt_version_tag'
Most of the work was done by tcberner@.
PR: 211916
Plasma5 ports
At the moment KDE ports use bsd.kde4.mk to handle their dependencies. When
working on the ports for KDE Frameworks and Plasma5 it seemed to be more
reasonable to create a new kde.mk instead of adding an bsd.kde5.mk.
The kde.mk in this review is a stripped down version of the one we are using in
the KDE Test repositories plasma5 branch [1] to only contain the parts relevant
to the current KDE4 ports in the portstree [2].
Changes to the KDE Ports needed by this:
Replace USE_KDE4 by USE_KDE [3]
Add USES=kde:4 [4]
[1] http://src.mouf.net/area51/view/branches/plasma5/KDE/Mk/Uses/kde.mk
[2] The version in the plasma5 branch also handles frameworks/plasma5 and
handles MASTER_SITES via a KDE_DIST variable similar to bsd.qt.mk for Qt
Ports -- I chose to leave this out for now, as the diff is already large
enough.
[3] I chose USE_KDE instead of USE_KDE4, USE_KDE5, USE_KDEX as the version we
want is already specified as argument to kde:<arg>
[4] For KDE Frameworks and Plasma5 ports this would be kde:5
PR: 210667
Approved by: portmgr, mat (mentor), rakuco (mentor)
Reviewed by: mat, rakuco
Differential Revision: https://reviews.freebsd.org/D6961
longer. This is a no-op because KDE4_PREFIX is equal to LOCALBASE
Fix up properties for misc/kde4-l10n/files/bsd.l10n.mk to make svn happy.
PR: 209014 (partial)
Submitted by: myself
Approved by: portmgr (bapt)
Differential Revision: https://reviews.freebsd.org/D6542
We basically need to revert a workaround inherited from a Qt commit from
2010 for a clang bug that has been fixed for many years. This workaround
coupled with proper support for -fvisibility=hidden I added to Phonon a
while ago was causing build problems in misc/qt4-qtdemo.
common changes:
- don't use deprecated USE_KDE4=kdehier
- drop deprecated @dirrmtry and use absolute path instead of @cwd
databases/akonadi:
- Update to 1.13.0
- add upstream patch to really avoid building Akonadi's unit tests
devel/grantlee:
- update to 0.5.1
devel/libkgapi:
- update to 2.2.0
devel/libkolab:
- update to 0.5.3
multimedia/phonon and multimedia/phonon-designerplugin:
- update to 4.8.1
multimedia/phonon-gstreamer:
- update to 4.8.0
- switch from GStreamer 0.10.x to 1.x
multimedia/phonon-vlc:
- update to 0.8.0
This is a minor bug fix release:
* Fix CMake 3 compatibility by synchronizing the FindQt4.cmake module from
kdelibs git.
* Prevent possible internal infinite loop call chains when trying to handle
backend construction in simulation mode (i.e. without actual backend being
installed on the system).
* When not building with PHONON_INSTALL_QT_EXTENSIONS_INTO_SYSTEM_QT, make
sure that the relative Qt paths are set according to whether the build is
meant for Qt4 or 5. Previously this would always install to a path for
qt5.
Get rid of the sed calls in the Makefile I abhor: the first one has been
replaced with an actual patch in files/ now that the file being patched has
changed, and the second one is not necessary anymore.
databases/akonadi to 1.7.2
devel/libdbusmenu-qt to 0.9.2
devel/qtscriptgenerator to 0.2.0
multimedia/phonon to 4.6.0
multimedia/phonon-gstreamer to 4.6.0
multimedia/phonon-vlc to 0.5.0
sysutils/qzeitgeist to 0.8.0
This should fix a warning (and, in bsam's case, an error) about a
wrong variable expansion in an if clause in CMake.
Approved by: avilla (mentor)
Feature safe: yes
