| View previous topic :: View next topic |
| Author |
Message |
moult
Retired Dev
Joined: 31 Mar 2008
Posts: 146
Location: Australia
|
 Posted: Tue Aug 01, 2017 9:56 pm Post subject: openvdb doesn't compile on arm platform |
 |
|
Lots of undefined references, and then ld exits. Not entirely sure what the cause is. Given that it is vdb_render failing, I suspect it is related to glew or glfw, both of which I have installed.
| Code: |
main.cc:(.text._ZN7openvdb6v4_0_04tree4TreeINS1_8RootNodeINS1_12InternalNodeINS4_INS1_8LeafNodeIdLj3EEELj3EEELj4EEEEEE5clearEv[
_ZN7openvdb6v4_0_04tree4TreeINS1_8RootNodeINS1_12InternalNodeINS4_INS1_8LeafNodeIdLj3EEELj3EEELj4EEEEEE5clearEv
]+0x404): undefined reference to `tbb::internal::allocate_root_with_context_proxy::allocate(unsigned int) const'
CMakeFiles/vdb_print.dir/cmd/openvdb_print/main.cc.o:main.cc:(.text._ZN7openvdb6v4_0_04tree4TreeINS1_8RootNodeINS1_12InternalNodeINS4_INS1_8LeafNodeIdLj3EEELj3EEELj4EEEEEE5clearEv[
_ZN7openvdb6v4_0_04tree4TreeINS1_8RootNodeINS1_12InternalNodeINS4_INS1_8LeafNodeIdLj3EEELj3EEELj4EEEEEE5clearEv
]+0x4b8): more undefined references to `tbb::internal::allocate_root_with_context_proxy::allocate(unsigned int) const' follow
collect2: error: ld returned 1 exit status
make[2]: *** [openvdb/CMakeFiles/vdb_print.dir/build.make:107: openvdb/vdb_print] Error 1
make[2]: Leaving directory '/var/tmp/portage/media-gfx/openvdb-4.0.0/work/openvdb-4.0.0_build'
make[1]: *** [CMakeFiles/Makefile2:168: openvdb/CMakeFiles/vdb_print.dir/all] Error 2
make[1]: Leaving directory '/var/tmp/portage/media-gfx/openvdb-4.0.0/work/openvdb-4.0.0_build'
make: *** [Makefile:139: all] Error 2
[31;01m*[0m ERROR: media-gfx/openvdb-4.0.0::gentoo failed (compile phase):
[31;01m*[0m emake failed
[31;01m*[0m
[31;01m*[0m If you need support, post the output of `emerge --info '=media-gfx/openvdb-4.0.0::gentoo'`,
[31;01m*[0m the complete build log and the output of `emerge -pqv '=media-gfx/openvdb-4.0.0::gentoo'`.
[31;01m*[0m The complete build log is located at '/var/tmp/portage/media-gfx/openvdb-4.0.0/temp/build.log'.
[31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/media-gfx/openvdb-4.0.0/temp/environment'.
[31;01m*[0m Working directory: '/var/tmp/portage/media-gfx/openvdb-4.0.0/work/openvdb-4.0.0_build'
[31;01m*[0m S: '/var/tmp/portage/media-gfx/openvdb-4.0.0/work/openvdb-4.0.0'
|
Full build log here:
https://paste.pound-python.org/show/fQIywYv6xw3gGSQYkazx/
Any ideas?
[Moderator edit: broke long whitespace-free lines in code tags to fix thread layout. -Hu]
_________________
thinkMoult - I write articles online. You might like some of them.
Planet Larry - do you write a blog and use Gentoo? Get your blog added to the Planet Larry Gentoo user blog aggregator! |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23135
|
| Posted: Wed Aug 02, 2017 12:43 am Post subject: |
|
|
| All the undefined references that I checked are for symbols in namespace tbb. The link line for vdb_print requests -ltbb, so my guess would be that library tbb exports fewer symbols on arm than on other platforms. Perhaps the symbols are conditionally compiled based on the target platform. Check that the requested symbols are exported from libtbb.so on arm and, if possible, also check on a platform where this package works correctly. |
|
| Back to top |
|
|
Chiitoo
Administrator
Joined: 28 Feb 2010
Posts: 2755
Location: Here and Away Again
|
| Posted: Thu Aug 10, 2017 10:45 am Post subject: |
|
|
Moved from Other Things Gentoo to Gentoo on Alternative Architectures, which might provide the topic with a bit more specific attention.
_________________
Kindest of regardses. |
|
| Back to top |
|
|
|
Gentoo on ARM
