-- Checking for module 'jack' -- No package 'jack' found CMake Error at server/scsynth/CMakeLists.txt:21 (message): Jack selected as audio API, but development files not found ----------------------------------------------------------------- This is an unstable amd64 chroot image (named 13.0-systemd-abi32+64_20170409-195332) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.5 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) *
Created attachment 469764 [details] emerge-info.txt
Created attachment 469766 [details] CMakeOutput.log
Created attachment 469768 [details] emerge-history.txt
Created attachment 469770 [details] environment
Created attachment 469772 [details] etc.portage.tbz2
Created attachment 469774 [details] media-sound:supercollider-3.8.0:20170411-182513.log
Created attachment 469776 [details] temp.tbz2
Which version of JACK do you have installed? It works for me with jack2 1.9.12 -- Found PkgConfig: x86_64-pc-linux-gnu-pkg-config (found version "0.29.2") -- Checking for module 'jack' -- Found jack, version 1.9.12 -- Found jack: /usr/lib/libjack.so -- Audio API: jack It seems like they're using this to find JACK: https://github.com/supercollider/supercollider/blob/develop/cmake_modules/FindJack.cmake
(In reply to Simon from comment #8) doesn't contains emerge-history.txt (139.37 KB, text/plain) the info ?
3.8.0 is gone from tree, was this reproduced with 3.9 yet?
I think this was a bug with the test/tinderbox, seems like it didn't install JACK (be it version 1 or 2).
Yes, but I wouldn't expect jack to be required when supercollider was configured with -jack ;)
Created attachment 544584 [details] emerge log for media-sound/supercollider-3.9.3-r1
(In reply to Andreas Sturmlechner from comment #12) > Yes, but I wouldn't expect jack to be required when supercollider was > configured with -jack ;) Euhm, that's a good point :P I just emerged media-sound/supercollider-3.9.3-r1 in a clean amd64 stage3, no custom USE flags set and it works fine, see attached log for more info. Excerpt from the configure output: > -- Checking for module 'portaudio-2.0' > -- Found portaudio-2.0, version 19 > -- Audio API: portaudio > -- Found ALSA: /usr/lib/libasound.so (found version "1.1.6")
Fine, let's consider it fixed.