Re: [Rivendell] Re: [Audacity-devel] Problem with libsoundtouch
On Tue, Apr 08, 2008 at 04:15:59PM -0000, Richard Ash wrote:
> Federico Grau wrote:
> > Last Friday I finally got access to the debian multimedia repository and I
> > am
> > trying to get the "soundtouch" problem with audacity in debian,ubuntu
> > put down ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459198 ).
> >
> > Bob, I apologize, you were correct in that libsoundtouch-dev is installed
> > and
> > not getting detected correctly. Lib soundtouch is correctly a build
> > dependency of Audacity... unfortunately it seems that pkg-config is not
> > correctly detecting the soundtouch library on debian,ubuntu systems.
> >
> > The challenge appears to be that debian (not sure about ubuntu,
> > packages.ubuntu.com is not responding for me right now) has soundtouch
> > 1.3.0
> > for all versions (stable, testing, unstable) ... they are "looking" into
> > updating, but that's still slowly moving along (
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462643 ).
> >
> > With the upstream 1.3.0 package of soundtouch there is no default
> > pkg-config file, so debian added one called "libSoundTouch" . The
> > problem is audacity is looking for "soundtouch" and thus not finding the
> > debian pkg-config info.
> >
> > Upstream, 1.3.1 of soundtouch appears to generate a pkg-config with name
> > "soundtouch-1.0.pc"
> >
> > # from soundtouch 1.3.1 Makefile.am
> > pkgconfigdir = $(libdir)/pkgconfig
> > pkgconfig_DATA = soundtouch-1.0.pc
>
> It does indeed, that's where I got the name used in the audacity configure
> script from (as Gentoo have been shipping 1.3.1 for a long time).
>
> > What should the correct approach be to settle this confusion ...
> > 1) should the debian package have a local patch looking for "whatever
> > it's soundtouch is" (likely emulated by ubuntu)?
> >
> > 2) should audacity acinclude.m4 check for various pkg-config names
> > (ex: soundtouch, soundtouch-1.0, libSoundTouch)
> >
> > 3) is there another better solution?
> Fix the debian/ubuntu package of soundtouch to create the correct
> pkg-config file? After all, this will affect every other application that
> uses pkg-config to find soundtouch, and presumably there is an intention
> to upgrade to the current version of soundtouch at some point this decade
> (at which point anyone using only the debian name will break).
>
> I don't like making audacity's scripts look for lots of names, because it
> defeats the point of pkg-config, i.e. there is a standard way to look for
> the presence and version of a package, regardless of where it is
> installed.
>
> So probably "if you start hacking stuff, you just have to keep on hacking"
> and patch the ubuntu builds of audacity.
>
Hi Richard,
Thanks for the response. Agreed as per the "start hacking stuff" mess. I am
still becoming familiar with pkg-config, but it seems that the libsoundtouch
version 1.3.1 creates "soundtouch-1.0.pc", not "soundtouch.pc" . A quick test
shows that the current audacity test still will not pick it up.
debiansid:~# cp /usr/lib/pkgconfig/libSoundTouch.pc /usr/lib/pkgconfig/soundtouch-1.0.pc
debiansid:~# pkg-config --exists --print-errors soundtouch
Package soundtouch was not found in the pkg-config search path.
Perhaps you should add the directory containing `soundtouch.pc'
to the PKG_CONFIG_PATH environment variable
No package 'soundtouch' found
debiansid:~# pkg-config --exists --print-errors soundtouch-1.0
debiansid:~# echo $?
0
Before I go asking folks to switch to a different pkg-config name, what should
the final target be (if simply "soundtouch", then I should contact the
soundtouch developer and ask him to change things upstream)? Is the gentoo
package of soundtouch patched to change its pkg-config file?
regards,
donfede
--
Federico Grau
Free Software Developer and Sysadmin
Radio Free Asia
2025 M Street, NW
Suite 300
Washington, DC 20036
202-587-2046 Telephone
202-721-7468 Facsimile
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and may
contain information that is privileged and confidential. Any unauthorized
dissemination, distribution, or copying is strictly prohibited. If you
receive this transmission in error, please contact network@rfa.org.
Reply to: