Bug#686777: netjack2 + opus custom modes + debian

[Adrian Knoth]

On 06/30/2013 03:11 AM, Ron wrote:

Hi!

I'll limit my response to the aspect of symbols, since Robin has already
answered the other questions.


>> Just sketching now:
>>
>> libopus0 will provide /usr/lib/libopus.so.0 (business as usual)
>> libopus-custom-0 will provide /usr/lib/libopus-custom.so.0
> 
> The big problem with this is that both of those will provide all of
> the functions that libopus.so.0 does, only some of the symbols with
> the same names will have different implementations in the -custom one.
> 
> Which means that when jack links to -custom, and jill links to -vanilla,
> and then some high level audio app or desktop environment or whatever
> links to both jack and jill ...   hilarity is likely to ensue.

I've seen colliding symbols with ardour via indirect linking, and it's
really a PITA to diagnose.

But here it seems to be very unlikely: only the jack server links
against libopus(-custom), and this server is a standalone binary that's
not linking or linked to anything else.

All the clients link against libjack, and even if they do link against
libopus, they're not interfering with the server's libopus-custom, since
client-server communication is done via /dev/shm.

So I think we can ignore the symbol aspect for all practical cases.
(Correct me if I'm wrong).



Cheers