Ok. Then I believe the next step is to double check what version of the
`libopus` your liquidsoap binary is linked with. Here's mine:
```
% ldd /usr/local/bin/liquidsoap
...
libopus.so.0 => /usr/lib/x86_64-linux-gnu/libopus.so.0
(0x00007f4f3ee58000)
....
```
Then, on a debian system, you can do:
```
% dpkg -L libopus0
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libopus.so.0.6.1
/usr/share
/usr/share/doc
/usr/share/doc/libopus0
/usr/share/doc/libopus0/changelog.Debian.gz
/usr/share/doc/libopus0/copyright
/usr/lib/x86_64-linux-gnu/libopus.so.0
```
So we're effectively using the debian packaged `libopus`. Finally:
```
% apt-cache show libopus0
Package: libopus0
Source: opus
Version: 1.3-1
Installed-Size: 383
Maintainer: Ron Lee <r...@debian.org>
Architecture: amd64
Depends: libc6 (>= 2.14)
Suggests: opus-tools
Description: Opus codec runtime library
Description-md5: 1155b70f2f801c41248e2e9c555bc1df
Multi-Arch: same
Homepage: http://www.opus-codec.org
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/main/o/opus/libopus0_1.3-1_amd64.deb
Size: 191080
MD5sum: 1feb55101b70f008e3b1968fb2005dca
SHA256: 78d2d72932f9749012cf356e8699f5f56c4a707eeb1f18c44b59928af7ac5876
```
Which gives us the version used for `libopus`.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/759#issuecomment-489155866
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
