Debian 12 FLAC & FFMPEG issue on LS 2.1.4 via OPAM

[TheRealMattLear]

Describe the bug
New opam installation on Debian 12 with both flac and ffmpeg results in a failed build. installation without ffmpeg package is working successfully.

To Reproduce

opam switch create 4.12.1;
eval `opam config env`;
eval $(opam config env);
opam install liquidsoap ffmpeg flac;

Results in:

[ERROR] The compilation of liquidsoap failed at "/usr/local/mediacp/.opam/opam-init/hooks/sandbox.sh build make".

#=== ERROR while compiling liquidsoap.2.1.4 ===================================#
# context     2.0.9 | linux/x86_64 | ocaml-base-compiler.4.12.1 | https://opam.ocaml.org#6ed4e23f
# path        ~/.opam/4.12.1/.opam-switch/build/liquidsoap.2.1.4
# command     ~/.opam/opam-init/hooks/sandbox.sh build make
# exit-code   2
# env-file    ~/.opam/log/liquidsoap-393849-f33fa5.env
# output-file ~/.opam/log/liquidsoap-393849-f33fa5.out
### output ###
# [...]
# /usr/bin/ld: warning: libFLAC.so.12, needed by /lib/x86_64-linux-gnu/libsndfile.so.1, may conflict with libFLAC.so.8
# /usr/bin/ld: /lib/x86_64-linux-gnu/libsndfile.so.1: undefined reference to `lame_encode_buffer_interleaved_ieee_double'
# /usr/bin/ld: /lib/x86_64-linux-gnu/libsndfile.so.1: undefined reference to `lame_encode_buffer_ieee_float'
# /usr/bin/ld: /lib/x86_64-linux-gnu/libsndfile.so.1: undefined reference to `lame_encode_buffer_ieee_double'
# /usr/bin/ld: /lib/x86_64-linux-gnu/libsndfile.so.1: undefined reference to `lame_encode_buffer_interleaved_int'
# /usr/bin/ld: /lib/x86_64-linux-gnu/libsndfile.so.1: undefined reference to `lame_encode_buffer_interleaved_ieee_float'
# collect2: error: ld returned 1 exit status
# File "caml_startup", line 1:
# Error: Error during linking (exit code 1)
# make[1]: *** [Makefile:377: liquidsoap] Error 2
# make[1]: Leaving directory '/usr/local/mediacp/.opam/4.12.1/.opam-switch/build/liquidsoap.2.1.4/src'
# make: *** [Makefile:10: all] Error 2

Version details

• OS: Debian 12
• Version 2.1.4

Install method
opam

[toots]

Hi @TheRealMattLear ! This seems to be a problem with the underlying C libraries. Did you do an upgrade of your debian installation? At any rate, it looks like libmp3lame shared library is missing from your system.

[vitoyucepi]

Probably the issue is caused by some of these

• 3rd party repos;
• dirty opam switch;
• mix of packages from different versions.

I've tried, but failed, to replicate this behavior by installing everything in Debian 11 and then updating it to Debian 12.
This is the script I used.

apt-get install wget curl make gcc patch unzip bubblewrap git
bash -c "sh <(curl -fsSL https://raw.githubusercontent.com/ocaml/opam/master/shell/install.sh)"
opam init --bare
opam switch create 4.12.1
eval $(opam env --switch=4.12.1)
opam install liquidsoap ffmpeg flac
sed 's/bullseye/bookworm/' -i /etc/apt/sources.list
apt-get update
apt-get dist-upgrade 
reboot
opam switch remove 4.12.1
opam switch create 4.12.1
eval $(opam env --switch=4.12.1)
opam install liquidsoap ffmpeg flac

1. The last ocaml release <5 is 4.14.1.

2. The current opam version is 2.1.5.

3. I have both versions of flac installed.

   ii  libflac12:amd64                   1.4.2+ds-2                     amd64        Free Lossless Audio Codec - runtime C library
   ii  libflac8:amd64                    1.3.3-2+deb11u1                amd64        Free Lossless Audio Codec - runtime C library
   

   apt list --installed | grep installed,local

   cpp-10/now 10.2.1-6 amd64 [installed,local]
   gcc-10-base/now 10.2.1-6 amd64 [installed,local]
   gcc-10/now 10.2.1-6 amd64 [installed,local]
   gcc-9-base/now 9.3.0-22 amd64 [installed,local]
   libaom0/now 1.0.0.errata1-3 amd64 [installed,local]
   libavcodec58/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
   libavdevice58/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
   libavfilter7/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
   libavformat58/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
   libavutil56/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
   libbpf0/now 1:0.3-2 amd64 [installed,local]
   libcbor0/now 0.5.0+dfsg-2 amd64 [installed,local]
   libcodec2-0.9/now 0.9.2-4 amd64 [installed,local]
   libdav1d4/now 0.7.1-3 amd64 [installed,local]
   libdns-export1110/now 1:9.11.19+dfsg-2.1 amd64 [installed,local]
   libffi7/now 3.3-6 amd64 [installed,local]
   libflac8/now 1.3.3-2+deb11u1 amd64 [installed,local]
   libgcc-10-dev/now 10.2.1-6 amd64 [installed,local]
   libicu67/now 67.1-7 amd64 [installed,local]
   libigdgmm11/now 20.4.1+ds1-1 amd64 [installed,local]
   libisc-export1105/now 1:9.11.19+dfsg-2.1 amd64 [installed,local]
   libldap-2.4-2/now 2.4.57+dfsg-3+deb11u1 amd64 [installed,local]
   libllvm11/now 1:11.0.1-2 amd64 [installed,local]
   libmpdec3/now 2.5.1-1 amd64 [installed,local]
   libperl5.32/now 5.32.1-4+deb11u2 amd64 [installed,local]
   libpostproc55/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
   libprocps8/now 2:3.3.17-5 amd64 [installed,local]
   libpython3.9-minimal/now 3.9.2-1 amd64 [installed,local]
   libpython3.9-stdlib/now 3.9.2-1 amd64 [installed,local]
   libsepol1/now 3.1-1 amd64 [installed,local]
   libsrt1.4-gnutls/now 1.4.2-1.3 amd64 [installed,local]
   libssl1.1/now 1.1.1n-0+deb11u5 amd64 [installed,local]
   libswresample3/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
   libswscale5/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
   libtiff5/now 4.2.0-1+deb11u4 amd64 [installed,local]
   liburing1/now 0.7-3 amd64 [installed,local]
   libvpx6/now 1.9.0-1 amd64 [installed,local]
   libwebp6/now 0.6.1-2.1+deb11u1 amd64 [installed,local]
   libx264-160/now 2:0.160.3011+gitcde9a93-2.1 amd64 [installed,local]
   libx265-192/now 3.4-2 amd64 [installed,local]
   linux-image-5.10.0-23-cloud-amd64/now 5.10.179-1 amd64 [installed,local]
   perl-modules-5.32/now 5.32.1-4+deb11u2 all [installed,local]
   python3.9-minimal/now 3.9.2-1 amd64 [installed,local]
   python3.9/now 3.9.2-1 amd64 [installed,local]
   

@TheRealMattLear, could you try cleaning your opam switch?

[TheRealMattLear]

@vitoyucepi thanks for your testing, this is actually a Debian 12 install (not upgrade) however there are a number of packages already on the system so there might be a conflict with an existing package on the system. I did test on a fresh D12 install and it worked fine so now i'm just working to pinpoint where this particular issue is. Will keep updated!

[TheRealMattLear]

Sorry for the delay following this up further, we decided to delay D12 support for future release to get our existing one out sooner than later. The problem obviously is a conflicting package and the issue is only occurring after running our software's installer. We've compiled a list of packages and steps being deployed by our software's installer but are struggling to replicate the conditions. Planning to investigate further again this week.

Should anyone have any advise based on the currently provided information that would be wonderful!