25 Sep
2007
25 Sep
'07
6:47 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have just built jack 0.107 from svn. I had to install it over the
jack installed from the ubuntu repository, which made me a bit
uncomfortable, but it got Ingen working, and it should get the latest
ardour from svn working with its midi editor, so I could live with
that. It broke qjackctl, but that gave me the opportunity to build a
newer version with jack midi support, so I could live with that too.
However it seems to have broken a whole lot of other jack apps, such
as hydrogen and alsaplayer, and I definitely can't live with that.
Is there a way to get 0.107 working with clients compiled against
older versions of jack?
Failing that, would I be able to get all these apps to work again
against the new version of jack if I simply build my own packages
from source debs, or would I run into further trouble?
Best
Robert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG+MsryQ3sfGecJBIRAkm8AJ9Vtl+nc7nI214pPsOzQlRF2Gu8xACgxOtX
mX77ese/ZO8AgzmXDmhbkRA=
=1Gxf
-----END PGP SIGNATURE-----
25 Sep
25 Sep
7:03 a.m.
New subject: getting jack 0.107 working with cclients compiled against earlier versions
Hi,
Am Dienstag, 25. September 2007 schrieb Robert Persson:
I have just built jack 0.107 from svn. I had to
install it over the
jack installed from the ubuntu repository, which made me a bit
uncomfortable, but it got Ingen working, and it should get the latest
ardour from svn working with its midi editor, so I could live with
that. It broke qjackctl, but that gave me the opportunity to build a
newer version with jack midi support, so I could live with that too.
However it seems to have broken a whole lot of other jack apps, such
as hydrogen and alsaplayer, and I definitely can't live with that.
Is there a way to get 0.107 working with clients compiled against
older versions of jack?
Sort of: You have to start these apps in a bash/shell where the
LD_LIBRARY_PATH points to your self-compiled jack-libs before the systems
jack-libs.
NOTE: This is a trick rather common in developing, but its not easy and for
every day usage of normal users. So if you stumble across this (in the
archives) and have no idea what this is about, _don't even think about it_!
Thats also the reason why I don't give any more details above. If you know how
to achieve it, you are okay to use it but otherwise just ignore this mail...
Arnold
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a rm / -rf. Or ask your
administrator to do so...
10:46 a.m.
New subject: getting jack 0.107 working with cclients compiled against earlier versions
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arnold Krille wrote:
Hi,
Am Dienstag, 25. September 2007 schrieb Robert Persson:
Is there a way to get 0.107 working with clients compiled against
older versions of jack?
Sort of: You have to start these apps in a bash/shell where the
LD_LIBRARY_PATH points to your self-compiled jack-libs before the
systems jack-libs.
NOTE: This is a trick rather common in developing, but its not easy
and for every day usage of normal users. So if you stumble across
this (in the archives) and have no idea what this is about, _don't
even think about it_! Thats also the reason why I don't give any
more details above. If you know how to achieve it, you are okay to
use it but otherwise just ignore this mail...
Yes that does make sense. That would still mean that I would not be
able to run apps compiled for different versions of jack on the same
jack server, but presumably if I were to compile a second copy of
those apps I want to use with the home-rolled version of jack then I
could also run those from a shell script too. Complicated, but
certainly preferable than getting in a mess with your package manager.
Many thanks for the useful tip.
Robert.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG+QMTyQ3sfGecJBIRAhdnAKDtw4uSHB3VjCON7+bE1crO1HWj9wCg3M7d
LQ3IU8/aCe6aP+rr+5RWsu4=
=48kA
-----END PGP SIGNATURE-----
11:24 a.m.
New subject: getting jack 0.107 working with cclients compiled against earlier versions
On Tue, 2007-09-25 at 01:47 -0700, Robert Persson wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have just built jack 0.107 from svn. I had to install it over the
jack installed from the ubuntu repository, which made me a bit
uncomfortable, but it got Ingen working, and it should get the latest
ardour from svn working with its midi editor, so I could live with
that. It broke qjackctl, but that gave me the opportunity to build a
newer version with jack midi support, so I could live with that too.
However it seems to have broken a whole lot of other jack apps, such
as hydrogen and alsaplayer, and I definitely can't live with that.
Is there a way to get 0.107 working with clients compiled against
older versions of jack?
Failing that, would I be able to get all these apps to work again
against the new version of jack if I simply build my own packages
from source debs, or would I run into further trouble?
What JACK package did you have installed? Older ones change the libjack
name to libjack-0.100.0, which all your packaged JACK programs would be
linked against, so the packaged JACK clients and the clients that you've
built yourself will use different libraries (which is not good, since
they may use different binary protocols to talk to jackd).
The way I do this is to build JACK from source (with --prefix=/usr),
install it over the packaged version, remove all files that start
with /usr/lib/libjack-0.100.0* and then
link /usr/lib/libjack-0.100.0.so.0 to /usr/lib/libjack.so. This way all
JACK clients will link to the same library, and as long as they use the
same library API that should work (although the library API changes
sometimes too).
More recent JACK packages for Debian (and I think Ubuntu) don't change
the library name, so you shouldn't have to do those steps in the future.
There are probably cleaner ways of doing this using APT magic, but I
haven't had any problems with this approach so far.
--ll
12:18 p.m.
New subject: getting jack 0.107 working with cclients compiled against earlier versions
On Tue, 2007-09-25 at 15:22 +0200, Lars Luthman wrote:
What JACK package did you have installed? Older ones change the libjack
name to libjack-0.100.0, which all your packaged JACK programs would be
and please note: ONLY Debian and Debian-derived distributions of Linux
have this issue. no other distribution has this problem, because the
name of the library was left alone. there is almost never a reason to
have to do anything to change JACK clients when you upgrade JACK if you
are on a system that didn't include this unnecessary name change.
--p
26 Sep
26 Sep
9:06 p.m.
New subject: getting jack 0.107 working with cclients compiled against earlier versions
Is there a way to get 0.107 working with clients
compiled against
older versions of jack?
Failing that, would I be able to get all these apps to work again
against the new version of jack if I simply build my own packages
from source debs, or would I run into further trouble?
yes start a jack client that is not working from the command line see what
version of jack it is trying to connect to find that file
libjack-[something].so and remove it - replace it with a symlink to version
you just installed.
Its a dirty hack but it seems to work often enough.
27 Sep
27 Sep
10:56 a.m.
New subject: getting jack 0.107 working with cclients compiled against earlier versions
Am Donnerstag, 27. September 2007 schrieb Danni Coy:
This is even more a trick from the
hope-you-know-what-you-are-doing-department.
And it opens pandoras box of _very_ strange error which come from changed abi
and changed api between the versions. And if you don't tell the devs on irc
or the mailing-lists that you did this _very_ dirty trick, they will try
to "fix" it for ages. If you tell them what you did, they tell you to either
undo it and check again or not complain about the errors...
So don't do this unless you know what it is about or know how to deal with the
results.
Arnold
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a rm / -rf. Or ask your
administrator to do so...
Is there a way
to get 0.107 working with clients compiled against
older versions of jack?
Failing that, would I be able to get all these apps to work again
against the new version of jack if I simply build my own packages
from source debs, or would I run into further trouble?
yes start a jack client
that is not working from the command line see what
version of jack it is trying to connect to find that file
libjack-[something].so and remove it - replace it with a symlink to version
you just installed.
Its a dirty hack but it seems to work often enough.
11:04 a.m.
New subject: getting jack 0.107 working with cclients compiled against earlier versions
On Thu, 2007-09-27 at 14:55 +0200, Arnold Krille wrote:
Am Donnerstag, 27. September 2007 schrieb Danni Coy:
This is even more a trick from the
hope-you-know-what-you-are-doing-department.
actually, its from
hope-you-know-what-you-are-doing-department-and-sorry-you-run-debian
department.
i have absolutely nothing personal against the debian JACK packager, but
words cannot begin to express the appalling state of affairs that the
misguided addition of -VERSION to the JACK library name has caused for
Debian users of JACK, along with most Ubuntu and other
derived-distributions. i would say we see at least 1-2 people per week
on the #ardour IRC channel who face the problem caused by this decision.
Even though it has been fixed now, its effects will linger on for at
least another year, perhaps even more. its a very frustrating thing for
me as a JACK developer to see different people bumping into this over
and over again, a situation that makes it appear that JACK has design
problems when all it really suffers from is a package design error.
--p
Is there
a way to get 0.107 working with clients compiled against
older versions of jack?
Failing that, would I be able to get all these apps to work again
against the new version of jack if I simply build my own packages
from source debs, or would I run into further trouble?
yes start a jack client
that is not working from the command line see what
version of jack it is trying to connect to find that file
libjack-[something].so and remove it - replace it with a symlink to version
you just installed.
Its a dirty hack but it seems to work often enough. 
3:26 p.m.
New subject: getting jack 0.107 working with cclients compiled against earlier versions
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Sep 27, 2007 at 09:04:28AM -0400, Paul Davis wrote:
On Thu, 2007-09-27 at 14:55 +0200, Arnold Krille
wrote:
I am very glad it has been fixed!
Would recommending that people upgrade to sid solve this problem?
- -ken
Am Donnerstag, 27. September 2007 schrieb Danni
Coy:
This is even more a trick from the
hope-you-know-what-you-are-doing-department.
actually, its from
hope-you-know-what-you-are-doing-department-and-sorry-you-run-debian
department.
i have absolutely nothing personal against the debian JACK packager, but
words cannot begin to express the appalling state of affairs that the
misguided addition of -VERSION to the JACK library name has caused for
Debian users of JACK, along with most Ubuntu and other
derived-distributions. i would say we see at least 1-2 people per week
on the #ardour IRC channel who face the problem caused by this decision.
Even though it has been fixed now, its effects will linger on for at
least another year, perhaps even more. its a very frustrating thing for
me as a JACK developer to see different people bumping into this over
and over again, a situation that makes it appear that JACK has design
problems when all it really suffers from is a package design error.
Is there
a way to get 0.107 working with clients compiled against
older versions of jack?
Failing that, would I be able to get all these apps to work again
against the new version of jack if I simply build my own packages
from source debs, or would I run into further trouble?
yes start a jack client
that is not working from the command line see what
version of jack it is trying to connect to find that file
libjack-[something].so and remove it - replace it with a symlink to version
you just installed.
Its a dirty hack but it seems to work often enough. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG++cie8HF+6xeOIcRAhwLAKCrjq+1/4A6TE9/FHMqMECUNcq3wACgoGCs
Mi1d2cSfz+CmGH6u7gymGpM=
=m+mM
-----END PGP SIGNATURE-----
4:10 p.m.
New subject: getting jack 0.107 working with cclients compiled against earlier versions
On Thu, 2007-09-27 at 10:23 -0700, Ken Restivo wrote:
On Thu, Sep 27, 2007 at 09:04:28AM -0400, Paul Davis
wrote:
No need, it's in Testing already.
--ll
i have absolutely nothing personal against the
debian JACK packager, but
words cannot begin to express the appalling state of affairs that the
misguided addition of -VERSION to the JACK library name has caused for
Debian users of JACK, along with most Ubuntu and other
derived-distributions. i would say we see at least 1-2 people per week
on the #ardour IRC channel who face the problem caused by this decision.
Even though it has been fixed now, its effects will linger on for at
least another year, perhaps even more. its a very frustrating thing for
me as a JACK developer to see different people bumping into this over
and over again, a situation that makes it appear that JACK has design
problems when all it really suffers from is a package design error.
I am very glad it has been fixed!
Would recommending that people upgrade to sid solve this problem?
6057
days inactive
6059
days old
linux-audio-user@lists.linuxaudio.org
9 comments
6 participants
participants (6)
-
Arnold Krille -
Danni Coy -
Ken Restivo -
Lars Luthman -
Paul Davis -
Robert Persson