Bug 105666 - Beignet build fails with llvm 3.9
Summary: Beignet build fails with llvm 3.9
Alias: None
Product: Beignet
Classification: Unclassified
Component: Beignet (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Zhigang Gong
QA Contact:
Depends on:
Reported: 2018-03-21 17:28 UTC by sami.khawaja
Modified: 2018-10-12 21:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Complete Build Log (309.26 KB, text/x-log)
2018-03-21 17:28 UTC, sami.khawaja

Description sami.khawaja 2018-03-21 17:28:51 UTC
Created attachment 138255 [details]
Complete Build Log

I am trying to build Beignet 1.3 with LLVM 3.9 to enabled OPEN_CL 2.0 on my platform.

But the build fails with following error,

[ 55%] Linking CXX shared library libgbe.so
/usr/bin/ld: /usr/lib/llvm-3.9/lib/libclangFrontend.a(CompilerInstance.cpp.o): unrecognised relocation (0x2a) in section `.text._ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EED2Ev[_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EED5Ev]'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
backend/src/CMakeFiles/gbe.dir/build.make:1756: recipe for target 'backend/src/libgbe.so' failed
make[2]: *** [backend/src/libgbe.so] Error 1
CMakeFiles/Makefile2:238: recipe for target 'backend/src/CMakeFiles/gbe.dir/all' failed
make[1]: *** [backend/src/CMakeFiles/gbe.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2

The complete build log is attached with this bug.
Comment 1 GitLab Migration User 2018-10-12 21:26:27 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/beignet/beignet/issues/61.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.