diff options
author | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2015-08-26 17:06:18 +0200 |
---|---|---|
committer | Peter Korsgaard <peter@korsgaard.com> | 2015-08-26 23:01:10 +0200 |
commit | 2215b8a75edea384182f0511b6649306e60b55d1 (patch) | |
tree | e793ae3f74a0cab96a3ca4a34b2fb3914bca44c7 /package/python-can/python-can.mk | |
parent | 551971984c74c989bc5749380bf276980a9efa5c (diff) | |
download | buildroot-2215b8a75edea384182f0511b6649306e60b55d1.tar.gz buildroot-2215b8a75edea384182f0511b6649306e60b55d1.zip |
qt5: disable for static-only builds
Even though we have some specific code to support building Qt5 for
static-only configurations, it doesn't work. The first problem is that
our custom qmake.conf always passes -ldl, which makes a number of Qt5
config.tests fail at configure time. Once this problem is fixed by
removing -ldl from QMAKE_LIBS and adding it to QMAKE_LIBS_DYNLOAD
instead, the next problem is that the plugin infrastructure of Qt5
assumes that Linux has dynamic library support: the qlibrary_unix.cpp
file includes <dlfcn.h>, and the only condition for this file to not
be included is:
Until recently, building Qt5 statically was working because our C
library was not built static-only: it provided <dlfcn.h> and
libdl.so. But now that we have a really static only toolchain, Qt5 no
longer builds.
The easiest solution is to simply make Qt5 depend on dynamic library
support.
Fixes:
http://autobuild.buildroot.net/results/538/538e0325adba9fabbe4ec8e550fbb6a7219f5e7a/
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package/python-can/python-can.mk')
0 files changed, 0 insertions, 0 deletions