some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
have been missed previously listed because Qt likes to dlopen() things
so check-lib-depends can't find it, which would stop qt4 getting updated
when ssl/crypto libs are updated.
/usr/local/lib/qt4/bin/findtr: a /usr/bin/perl -w script text executable
/usr/local/lib/qt4/bin/syncqt: a /usr/bin/perl -w script text executable
These are both perl scripts, so use INSTALL_SCRIPT instead of
INSTALL_PROGRAM.
While here: qt-project.org -> qt.io in some comments.
FD_SETSIZE (1024 by default) file descriptors. This is often the case
for KDE4 apps when using libinotify as directory monitoring backend.
Positive feedback from deraadt@, final okay sthen@
It was the same story again: TLSv1_*_method() are TLSv1.0, not TLSv1.x.
Should fix problems landry@ and sthen@ (and likely others) were seeing.
Joint work with and final okay sthen@
/usr/local/bin/lconvert4 -> /usr/local/lib/qt4/bin/lconvert
is created.
Fixes a mail/trojita build failure spotted by ajacoutot.
lconvert was introduced with Qt-4.5, so we probably forgot to add
it to ${PROGRAMS4} at the time...
Tested in a bulk. OK ajacoutot@, zhuk@
through the PLT, so do on OpenBSD what Linux and FreeBSD are already doing.
Fixes build with binutils 2.17 and fixes a potential runtime issue with
binutils 2.15.
ok espie@
okay espie@ (MAINTAINER), went through a couple of KDE4 builds.
This should been committed a while ago. Even more, I was thinking that this
patch *was* committed at Oct 22... It's probably better late than never.
No point in trying to build it for days before seeing it failing horribly
because hppa/atomic ops/webkit... there might be an easy fix/workaround;
but right now hope is lost.
context-dependent attackers to cause a denial of service (memory
consumption) via an XML Entity Expansion (XEE) attack
From upstream via Arch Linux
OK espie@ (maintainer)
The change which attempted to fix QTBUG-15319 broke keyboard shortcuts
for non latin keyboard layouts.
This patch reverts QTBUG-15319 (f45cdeda8) since it caused a
regression.
From upstream via Arch Linux.
OK espie@ (maintainer)
privilege-separated X and caused broken displays for applications using
qt frames, diff from dcoppa, okay espie.
(An alternative fix would be to disable shm support, i.e.
"CONFIGURE_ARGS += -no-mitshm", I'd prefer this but it would need further
testing).
via Arch Linux).
Feedback from zhuk@, espie@, and Amit Kulkarni.
ABI/API compatibility analysis done with abi-compliance-checker.
ok espie@ (MAINTAINER)
a new libmysqlclient non-blocking API which utilizes co-routines. The X86
specific GCC ASM co-routine support hid the fact that there was an issue.
The only fallback code so far is POSIX user contexts which OpenBSD does not
support.
Input from and Ok sthen@ jasper@
was present at configure time, so the build is non-deterministic.
(notably audio/musique build fails unless qt4 was built with gtk
theme support). Add gtk+2 as a build dep to avoid this. Sync WANTLIB
while there. ok espie@
