Summary: | media-libs/simage-1.8.0-r1[-sndfile] with libsndfile installed: libsimage.so: undefined reference to `sf_open' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert G. Siebeck <gentoo.2019> |
Component: | Current packages | Assignee: | Maciej Mrozowski <reavertm> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | ionen, jstein, waebbl-gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robert G. Siebeck
2021-02-16 09:32:06 UTC
Looks like a bug in =simage-1.8.0-r1 rather than freecad. sf_open and the like are from libsndfile which should, in theory, only be used with simage[sndfile]. However, despite USE=-sndfile, if =simage-1.8.0-r1 is built while libsndfile was available on the system it still references symbols from it (without linking): $ gcc -o test test.c `pkg-config --cflags --libs simage` -lm /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib64/libsimage.so: undefined reference to `sf_open' So anything using it will fail, not just freecad. No problems if I rebuild simage without libsndfile on the system. Changing summary given it's 1.8.0-r1 that's affected and 1.8.1 fixes the issue. Then again I'd argue it should instead read as: "media-libs/simage-1.8.1 stabilization" The issue has been know for <simage-1.8.1 for some time, see for example https://github.com/waebbl/waebbl-gentoo/issues/274 for discussion on that topic and https://github.com/coin3d/simage/issues/46 for fixes in 1.8.1 of this issue. We could either stabilize 1.8.1, IMO it's been around long enough, or explicitly depend freecad on >=media-libs/simage-1.8.1. *** This bug has been marked as a duplicate of bug 708894 *** |