summaryrefslogtreecommitdiffstats
path: root/package/moarvm/Config.in
diff options
context:
space:
mode:
authorYann E. MORIN <yann.morin.1998@free.fr>2017-02-23 23:17:13 +0100
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2017-02-26 21:45:22 +0100
commitdbd30cd5d8d1970e2838ffb59d0179a1524b0ce4 (patch)
tree971b735355ba7dd3dea32d3764b8d9555cd25651 /package/moarvm/Config.in
parent410082e1d980668385ffd2993920785e0fffd2c1 (diff)
downloadbuildroot-dbd30cd5d8d1970e2838ffb59d0179a1524b0ce4.tar.gz
buildroot-dbd30cd5d8d1970e2838ffb59d0179a1524b0ce4.zip
package/directfb: disable for static builds
DirectFB is written in C++, but can be linked to by a C library or program. When doing shared link, this is fine because the linker gets help from the DT_NEEDED flags and knows what libraries to pull in during the link. However, during a static link, the linker does not get such help. Properly fixing this would require that there is support in pkg-config and autotools to specify that the C++ runtime must be linked. Alas there is no sush support. The only option is to add -lstdc++ to the Libs.Private field in directfb.pc. But this is not upstreamable, because there are other C++ runtimes in the wild (e.g. -lc++ from llvm/clang). However, DirectFB in a static scenario is probably not a very common scenario. Disable DirectFB for static builds. Fixes: http://autobuild.buildroot.org/results/3d3/3d3036d40ddad71d872d910aae7a24975706d2e9/ http://autobuild.buildroot.org/results/d1c/d1c35a6003396942b584f2f2a5e8bf4ac2fbe370/ http://autobuild.buildroot.org/results/d45/d4504871bd47930e8363032d380cdfcc5bb8aee7/ [...] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/moarvm/Config.in')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud