[64studio-devel] [Jackit-devel] jackd 0.103.0: jackd: symbol lookup error: jackd: undefined symbol: jack_zero_filled_buffer

[Free Ekanayaka]

Hi all,

|--==> Quentin Harley writes:

  QH> Paul Davis wrote:
  >>On Fri, 2007-04-27 at 21:51 +0000, Jürgen Schöneberg wrote:
  >>
  >>>Hello!
  >>>
  >>>I dont know, but I tried to upgrade jack with packages from debian sid 
  >>>and I tried it also by installing from source (make install)
  >>>
  >>>
  >>>in /usr/lib it looks like:
  >>>
  >>>/usr/lib/libjack0.100.0
  >>>/usr/lib/libjack-0.100.0.so.0
  >>>/usr/lib/libjack.la
  >>>/usr/lib/libjack.so
  >>>/usr/lib/libjack.so.0
  >>>/usr/lib/libjack.so.0.0.23
  >>>
  >>

If you have upgraded from a plain Debian system to the the latest
0.103.0-1 jack package in unstable then,

/usr/lib/libjack0.100.0
/usr/lib/libjack-0.100.0.so.0

should be only symbolic links. They are there to let the packages
compiled against the old jack-dev package keep working, till when the
transition to the new jack package will be over (i.e. till when all
jack dependant packages will be rebuilt).

  >>DEBIAN ALERT. Either give up now, or please google for "debian jack
  >>problem". You have two copies of JACK installed, which is not a good
  >>idea and on Debian in particular, its a disaster. You need to forcibly
  >>remove one or both of them and start over. If you are going to install
  >>the source code package you MUST use --prefix=/usr and on Debian you
  >>must create a symlink to match the library name that Debian has made all
  >>JACK client packages link to.

This should be no longer necessary, the symlink are created
automatically by the latest libjack0 package in unstable. So now
simply compiling and installing jack from source with --prefix=/usr
should just work.

  >>
  >>BTW, i got a notice this week that Debian (more specifically, the JACK
  >>packager for Debian) has *finally* fixed their insane policy of messing
  >>with our library names. This isn't going to help people like Jurgen.

I'm sorry it took so long, the fix was actually read since at least
two months now, but the new package hasn't been uploaded not to
interfere with the Etch release. Then when Etch was released and the
new package uploaded, it has been hold in the NEW queue because the
name of the library binary package changed. It finally got to unstable
a few days ago.

  QH> Paul is right... been there - done that.

  QH> The debian guys - like 64studio - Please use apt-get or Synaptic to 
  QH> install your packages... or else please follow the instructions from the 
  QH> packagers very closely.  I first ran into this problem when I had to 
  QH> build jackd from scratch to test the integration of the clockfix 
  QH> branch.  Wasn't nice!  I messed it up so badly, I had to reinstall my 
  QH> distro to fix it.

Ok, from now it should be better, let me know if you still experience
problems.

Ciao,

Free