Unresolved symbols in the 3.0~dfsg-2 and 3.0~dfsg-3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
assimp (Ubuntu) |
Fix Released
|
Undecided
|
IOhannes m zmoelnig | ||
Bug Description
[Impact]
There is a bug in the packaging of Assimp (assimp-3.0~dfsg-2 and -3) shipped with Trusty and Vivid that strips some C++ symbols from the library. This makes it impossible to use the C++ API on those releases.
[Test Case]
I've attached an example program that demonstrates this bug (originally from: https:/
g++ assimp.cpp -o assimp-ex `pkg-config --libs assimp`
I expect this to succeed with no errors. On Trusty, this command fails with the following output:
/tmp/ccVfhC0C.o: In function `main':
assimp.
/tmp/ccVfhC0C.o: In function `aiReturn aiMaterial:
assimp.
/tmp/ccVfhC0C.o: In function `aiReturn aiMaterial:
assimp.
/tmp/ccVfhC0C.o: In function `aiReturn aiMaterial:
assimp.
collect2: error: ld returned 1 exit status
[Regression Potential]
This is fixed by adding a few entries to the 'debian/
(c++)"
(c++)"
(c++)"
(c++)"
(c++)"
(c++)"
(c++)"
All of these symbols start with "ai", the prefix used by all symbols in Assimp, so they should not conflict with any other libraries (and, if they do, it is likely that other symbols already exported will conflict as well).
This is fixed in 3.0~dfsg-4 (see: https:/
[Other Information]
$ lsb_release -rd
Description: Ubuntu 14.04.2 LTS
Release: 14.04
$ apt-cache policy libassimp3
libassimp3:
Installed: 3.0~dfsg-2
Candidate: 3.0~dfsg-2
Version table:
*** 3.0~dfsg-2 0
500 http://
100 /var/lib/
Note that this issue also applies to 3.0~dfsg-3. This affects Precise, Trusty, Utopic, and Vivid.
Status changed to 'Confirmed' because the bug affects multiple users.