[CM] linux-port of OpenMusic
nando at ccrma.Stanford.EDU
Tue Oct 29 19:24:16 PDT 2013
On 10/29/2013 03:40 PM, Ralf Mattes wrote:
> On Tue, Oct 29, 2013 at 11:17:09PM +0100, anders.vinjar at bek.no wrote:
>> R> I think that's not really a viable solution. At least libcelt
>> R> isn't even currently available in Debian stable/testing.
>> Then i guess your libjack doesnt need it?
> This is the Debian-provided libjack:
> ldd /usr/lib/x86_64-linux-gnu/libjack.so.0
> linux-vdso.so.1 (0x00007fff6afe8000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fec6650a000)
> libopus.so.0 => /usr/lib/libopus.so.0 (0x00007fec662c3000)
> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fec660ba000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fec65eb6000)
> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fec65bb3000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fec658b4000)
> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fec6569e000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fec652f2000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fec669c6000)
>> The jack-api in use in OM is very simple, and doesnt rely on anything
>> outside jack.h
Then dynamically linking against the native build of libjack should be
more than enough, no need to package .so binaries which will always lead
to problems (for example, libcelt is required by a certain build of
libjack but not others - if you use the native libjack the distribution
will take care of the proper library dependencies).
>> R> BTW, any chance to get a 64bit version?
>> If you provide me with a 'enterprise'-license for lw (= 3 times the
>> price of the 'pro'-license :-/ )
> Yeah, tell me. I was _almost: buying a LW Licence, until I saw that huge price
> tag on the 64bit version. 64bit == Enterpise, that's so 1990ish ;-)
>> R> I'm not shure a 32bit libjack will play nicely with a 64bit
>> R> jackd.
>> It usually does. What troubles do you see?
> None, since I couldn't get OM to run without libcelt. I just speculated, since
> libjack and jack need to work as a pair (i.e. jackd and libjack need to match)
> and from toying with jack on ARN I know that there are some struct packing issues.
Jack needs to be compiled with the -DJACK_32_64 option (at least jack2
does - there's also a compile flag but I forget the name), that creates
structures that can be accessed from the 32 and 64 worlds without
compatibility problems. I needed to do that for Planet CCRMA when chuck
was 32 bit only and our workstations were running 64 bit OSs. A Jack
that is built with that option will work with 32 bit apps on a 64 bit
More information about the Cmdist