Bugzilla Bug 46916

The interface exposed by ladcca seems to have changed between version 0.3.2 and
0.4.0, which breaks fluidsynth-1.0.3 (and probably previous versions) when
compiled with the "ladcca" USE flag.

Reproducible: Always
Steps to Reproduce:
1. emerge '=ladcca-0.4.0'
2. emerge '=fluidsynth-1.0.3'
Actual Results:  
The fluidsynth make process fails with these essential lines:

fluidsynth.c: In function `main':
fluidsynth.c:444: error: `CCA_Use_Jack' undeclared (first use in this function)
fluidsynth.c:444: error: (Each undeclared identifier is reported only once
fluidsynth.c:444: error: for each function it appears in.)
fluidsynth.c:447: error: `CCA_Use_Alsa' undeclared (first use in this function)

Expected Results:  
Fluidsynth should have been built and merged.

removed ladcca support from the fluidsynth ebuilds until a newer version gains
support for the newer ladcca.

this doesn't fix anything. if ladcca is already installed, fluidsynth will fail
to compile. i'm unmasking things on amd64 and snagged into this one while
seeing if museseq can be unmasked...

the dependency should be versioned or ladcca should be specifically disabled.

fluidsynth compiles and installs properly on amd64 using a versioned
dependency, so i've added it to the ebuild. i've made it amd64-specific so as
not to break ppc, which has fluidsynth marked stable but not the older
ladcca....

could someone from ppc take a look at this? if ladcca 0.3.2 can be marked
stable on ppc, then the arch-specific versioning can be removed.

also, since simply not enabling ladcca support doesn't disable it, i think i'm
supposed to use_enable here?

*pokes PPC guys with a stick*

/me runs around screaming, and carrying a large pole with a piece of beef
attached to it

Fixed both ladcca-0.3.2 and fluidsynth-1.0.3 on ppc.

Forgot to close ;)