Jimmy:
I think I did understand (after careful evaluation) each of the decision
points in the build process.
Having done this before (with David's help), I knew I was exposing my
test systems to some degree of risk. That's why I didn't use any of my
primary partitions for doing this testing.
--- On Sat, 8/4/12, "Aere Greenway" wrote:
> Where it has been stated that there are no fluidsynth
> dependencies on
> jack, I think you should re-examine that claim, based on the
> problems I
> encountered.
Fluidsynth can be compiled with just Alsa, no need for Jack. So the claim is
valid
--- On Sun, 8/5/12, jimmy wrote:
> If you still don't understand what I have written, it would
> still be a big baffling mistery for you.
Sorry, "mystery" not "mistery".
More on decoding "apt-get" command you used. From the info you posted:
>>>
aere@Aere-HP-Vectra:~/fluidsynth-1.1.6$ sudo a
--- On Sun, 8/5/12, Aere Greenway wrote:
>
> The problem I am experiencing is with trying to run a test
> of the fluidsynth release candidate.
>
Again, the real problem was depencies around a package that was alread
installed on your system:
libjack-dev
which requires
libjack0
w
Jimmy:
The problem I am experiencing is with trying to run a test of the
fluidsynth release candidate.
The set of components I use work fine with jackd2, and that is what they
want (and install as dependencies).
When I attempt to build fluidsynth, it has a set of dependencies which
conflict
--- On Sun, 8/5/12, Aere Greenway wrote:
> Given the problems I had getting qjackctl to co-exist with
> the generated
> version of fluidsynth, I am puzzled by why I had no problems
> with my
> Ubuntu partition. My guesses why are as follows:
>
> 1. I had previously done some testing of a Rose
