29 Aug
2008
29 Aug
'08
8:49 p.m.
Maybe someone can help me out with this?
vamp-sdk appears to have no install targets, so I move everything
manually to their places, but the configure script for Rubber Band still
misses it. I'm running into all sorts of errors I've never seen before.
Within the vamp source directory, I can do:
make sdk
and get that to work okay. Then what? The README also says I need to
alter the Makefile to "suit my system", but when I try to change to
directory paths at the beginning to places like /usr/include/vamp and
/usr/local/lib/vamp-sdk, I just get an error saying those build targets
don't exist. I did use sudo.
Apparently, vamp needs to show up in something called PKG_CONFIG_PATH,
which right now on my system has absolutely nothing in it. I've read the
pkg-config man page, and am no closer to solving this issue.
Thanks for the help.
-- Darren Landrum
29 Aug
29 Aug
10:09 p.m.
2008/8/29 Darren Landrum <darren.landrum(a)sbcglobal.net>et>:
Maybe someone can help me out with this?
vamp-sdk appears to have no install targets, so I move everything
manually to their places, but the configure script for Rubber Band still
misses it. I'm running into all sorts of errors I've never seen before.
Within the vamp source directory, I can do:
make sdk
and get that to work okay. Then what? The README also says I need to
alter the Makefile to "suit my system", but when I try to change to
directory paths at the beginning to places like /usr/include/vamp and
/usr/local/lib/vamp-sdk, I just get an error saying those build targets
don't exist. I did use sudo.
Apparently, vamp needs to show up in something called PKG_CONFIG_PATH,
which right now on my system has absolutely nothing in it. I've read the
pkg-config man page, and am no closer to solving this issue.
Thanks for the help.
-- Darren Landrum
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Not a specific answer: Pkgconfig files are usually installed when you
install <packagename.>-dev packages.
If it is available via your distro install the apt-file package. Run
apt-file update, then apt-file search <filename>(get this from error
message when compiling) to find the required package.
--
rob
http://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=82BS4ZCMFR1
10:33 p.m.
Robin wrote:
Not a specific answer: Pkgconfig files are usually
installed when you
install <packagename.>-dev packages.
If it is available via your distro install the apt-file package. Run
apt-file update, then apt-file search <filename>(get this from error
message when compiling) to find the required package.
As amazingly handy of a tool that is, and thank you for pointing it out
to me, I'm afraid it doesn't help in this instance. When I run the
./configure on Rubber Band, I get this error:
--------------------------
checking for Vamp... configure: error: Package requirements (vamp-sdk)
were not met:
No package 'vamp-sdk' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables Vamp_CFLAGS
and Vamp_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
--------------------------
The thing is, I have the vamp-sdk compiled, and I tried to install it,
but it still didn't help at all. There's some kind of package management
trick I obviously don't know anything about.
-- Darren
30 Aug
30 Aug
3:45 a.m.
On Fri, Aug 29, 2008 at 08:33:13PM -0400, Darren Landrum wrote:
Robin wrote:
You mentioned, that you have to install vamp-sdk manually, so is there a
'vamp-sdk.pc'(or some other .pc-file) you missed? I'd guess the configure of
Rubber Band is asking pkg-config for information on vamp-sdk,
where pkg-config searches for some .pc-file in /usr/lib/pkgconfig which
contains information on vamp-sdk and returns a 'not found' if there is none.
v4hn
Not a specific answer: Pkgconfig files are
usually installed when you
install <packagename.>-dev packages.
If it is available via your distro install the apt-file package. Run
apt-file update, then apt-file search <filename>(get this from error
message when compiling) to find the required package.
As amazingly handy of a tool that is, and thank you for pointing it out
to me, I'm afraid it doesn't help in this instance. When I run the
./configure on Rubber Band, I get this error:
--------------------------
checking for Vamp... configure: error: Package requirements (vamp-sdk)
were not met:
No package 'vamp-sdk' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables Vamp_CFLAGS
and Vamp_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
--------------------------
The thing is, I have the vamp-sdk compiled, and I tried to install it,
but it still didn't help at all. There's some kind of package management
trick I obviously don't know anything about.
-- Darren 
4:05 a.m.
v4hn wrote:
On Fri, Aug 29, 2008 at 08:33:13PM -0400, Darren
Landrum wrote:
Hmmm, I did a search in my repositories (Debian Etch Lenny/Sid) and it
reports "vamp-plugin-sdk". Same thing? It also mentions a couple of libs
- libvamp-sdk1 and libvamp-hostsdk2.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Robin wrote:
You mentioned, that you have to install vamp-sdk manually, so is there a
'vamp-sdk.pc'(or some other .pc-file) you missed? I'd guess the configure of
Rubber Band is asking pkg-config for information on vamp-sdk,
where pkg-config searches for some .pc-file in /usr/lib/pkgconfig which
contains information on vamp-sdk and returns a 'not found' if there is none.
Not a specific answer: Pkgconfig files are
usually installed when you
install <packagename.>-dev packages.
If it is available via your distro install the apt-file package. Run
apt-file update, then apt-file search <filename>(get this from error
message when compiling) to find the required package.
As amazingly handy of a tool
that is, and thank you for pointing it out
to me, I'm afraid it doesn't help in this instance. When I run the
./configure on Rubber Band, I get this error:
--------------------------
checking for Vamp... configure: error: Package requirements (vamp-sdk)
were not met:
No package 'vamp-sdk' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables Vamp_CFLAGS
and Vamp_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
--------------------------
The thing is, I have the vamp-sdk compiled, and I tried to install it,
but it still didn't help at all. There's some kind of package management
trick I obviously don't know anything about.
-- Darren
10:15 a.m.
v4hn wrote:
You mentioned, that you have to install vamp-sdk
manually, so is there a
'vamp-sdk.pc'(or some other .pc-file) you missed? I'd guess the configure of
Rubber Band is asking pkg-config for information on vamp-sdk,
where pkg-config searches for some .pc-file in /usr/lib/pkgconfig which
contains information on vamp-sdk and returns a 'not found' if there is none.
I read through man pkg-config and found the relevant information, edited
and dropped the vamp.pc and vamp-sdk.pc files into place, and now, even
though Rubber Band's configure script now worked, it still couldn't
compile as it couldn't find the vamp libs. I really wish I knew why, and
why it is I'm having so much more trouble with this single lib then I've
ever had before with any other.
I'm ready to give up with a story about why mainstream music on the
Linux desktop will never happen.
-- Darren
10:44 a.m.
Am Samstag, den 30.08.2008, 08:14 -0400 schrieb Darren Landrum:
I read through man pkg-config and found the relevant information, edited
and dropped the vamp.pc and vamp-sdk.pc files into place, and now, even
though Rubber Band's configure script now worked, it still couldn't
compile as it couldn't find the vamp libs. I really wish I knew why, and
why it is I'm having so much more trouble with this single lib then I've
ever had before with any other.
I'm ready to give up with a story about why mainstream music on the
Linux desktop will never happen.
-- Darren
I dont now about ubuntu packages, but on debian I need to enable the
macro dh_makeshlibs (and dh_shlibdeps) in the /debian/rules to force the
build process to generate the xxx.pc files. That is necessary for all
development libs.
hope it helps hermann
10:59 a.m.
On Sat, Aug 30, 2008 at 08:14:55AM -0400, Darren Landrum wrote:
v4hn wrote:
Well, i suppose it's a pebkac issue, since i got no problem compiling and
installing both librarys. However I hate the way the vamp-sdk developers
sneak around using autoconf.
Did you adjust INSTALL_PREFIX in line 60 of Makefile to "/usr"?
Afterwards just a `make && make install` and vamp-sdk is installed.
Did i already mention I hate to adjust Makefiles manually?
v4hn
You mentioned, that you have to install vamp-sdk
manually, so is there a
'vamp-sdk.pc'(or some other .pc-file) you missed? I'd guess the configure of
Rubber Band is asking pkg-config for information on vamp-sdk,
where pkg-config searches for some .pc-file in /usr/lib/pkgconfig which
contains information on vamp-sdk and returns a 'not found' if there is none.
I read through man pkg-config and found the relevant information, edited
and dropped the vamp.pc and vamp-sdk.pc files into place, and now, even
though Rubber Band's configure script now worked, it still couldn't
compile as it couldn't find the vamp libs. I really wish I knew why, and
why it is I'm having so much more trouble with this single lib then I've
ever had before with any other.
I'm ready to give up with a story about why mainstream music on the
Linux desktop will never happen.
12:47 p.m.
v4hn wrote:
Well, i suppose it's a pebkac issue, since i got
no problem compiling and
installing both librarys. However I hate the way the vamp-sdk developers
sneak around using autoconf.
Did you adjust INSTALL_PREFIX in line 60 of Makefile to "/usr"?
Afterwards just a `make && make install` and vamp-sdk is installed.
Did i already mention I hate to adjust Makefiles manually?
No, I can't say I did do that because, you see, I've never, ever, had to
do that before with anything. I'm going to give installing Gentoo and
the Pro-Audio Overlay a shot at this point, in the hopes that their
LiveCD is finally fixed for my platform.
-- Darren
30 Aug
30 Aug
12:52 p.m.
Darren Landrum wrote:
v4hn wrote:
afaict, vamp-sdk is only needed to build the vamp-rubberband plugin.
it's not really needed to build librubberband
i remember i've done this when once built librubberband on, aham,
windows: edit and remove anything "vamp" from Makefile.in
oops, Chris Cannam might digress on this suggestion, though :o)
hth
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
You mentioned, that you have to install vamp-sdk
manually, so is there a
'vamp-sdk.pc'(or some other .pc-file) you missed? I'd guess the configure of
Rubber Band is asking pkg-config for information on vamp-sdk,
where pkg-config searches for some .pc-file in /usr/lib/pkgconfig which
contains information on vamp-sdk and returns a 'not found' if there is none.
I read through man pkg-config and found the relevant information, edited
and dropped the vamp.pc and vamp-sdk.pc files into place, and now, even
though Rubber Band's configure script now worked, it still couldn't
compile as it couldn't find the vamp libs. I really wish I knew why, and
why it is I'm having so much more trouble with this single lib then I've
ever had before with any other.
I'm ready to give up with a story about why mainstream music on the
Linux desktop will never happen.
11:54 p.m.
Rui Nuno Capela wrote:
afaict, vamp-sdk is only needed to build the
vamp-rubberband plugin.
it's not really needed to build librubberband
i remember i've done this when once built librubberband on, aham,
windows: edit and remove anything "vamp" from Makefile.in
Okay, after a nice break listening to some old vinyl records I got by
the arm-load from someone, I finally figured out that this problem can
be bypassed by running Rubber Band's configure script like this:
./configure Vamp_CFLAGS=no Vamp_LIBS=no
This basically shut off the need for Vamp. After that, I was able to get
Qtractor to compile and run with RB support.
Thanks for everyone who had patience with me.
Regards,
Darren Landrum
31 Aug
31 Aug
8:33 a.m.
On Fri, Aug 29, 2008 at 11:48 PM, Darren Landrum
<darren.landrum(a)sbcglobal.net> wrote:
vamp-sdk appears to have no install targets
Hang on -- the Makefile does have an install target. It installs
everything below /usr/local. Does "make install" fail to work for
you?
Chris
10:32 a.m.
Chris Cannam wrote:
Hang on -- the Makefile does have an install target.
It installs
everything below /usr/local. Does "make install" fail to work for
you?
I did "make sdk" because one of the example plug-ins doesn't want to
compile on my machine (no big deal), but when I did "sudo make install"
it just tried compiling everything again, which of course stopped once
it got to that one plug-in.
Yes, it is weird, and it makes me wonder if I did something stupid like
typo "install" or similar. Although I did finally get Rubber Band
working, which was my goal, I'll give Vamp another try later, as it does
look quite interesting, and I hadn't known about it before.
-- Darren Landrum
1 Sep
1 Sep
4:43 a.m.
New subject: A short compiling howto [was: Re: Compiling vamp-sdk and Rubber Band on Ubuntu Studio 64]
Here's my take on how to solve the pitfalls you might run into when
compiling stuff.
1. Make sure you've got the -devel packages needed.
If configure/make complains about "can't find libsamplerate" or
"jpeg.h missing" or similar, you probably haven't installed the -devel
packages for those programs.
2a. Make sure the linker can find the other libs/programs you compiled.
If you compile things and (per default, usually) install to /usr/local
you need
to make sure the linker finds those libs.
Create a file named local.conf in /etc/ld.so.conf.d and put
/usr/local/lib into it.
2b. Make sure pkgconfig can find your .pc files.
Set PKG_CONFIG_PATH to /usr/local/lib/pkgconfig.
3. Use stow. (Optional but IMHO very usefull)
Stow allows you to install compiled programs to any directory and link
the files to any other (usually /usr/local).
I usually do "./configure --prefix=/opt/<package-name-and-version>" to
install to, say, /opt/audacity-3.5.12 and then run
"stow -d /opt -t /usr/local audacity-3.5.12"
to create symbolic links from /opt/audacity-3.5.12 to /usr/local.
This way it's also very easy to uninstall any self-compiled program;
unstow using
"stow -D -d /opt/ -t /usr/local audacity-3.5.12"
and
"rm -rf /opt/audacity-3.5.12"
and everything's gone.
Using this approach it's also easy to try new new versions and keep
the old as backup.
- Peder
5719
days inactive
5722
days old
linux-audio-user@lists.linuxaudio.org
14 comments
8 participants
participants (8)
-
Chris Cannam -
Darren Landrum -
david -
hermann meyer -
Peder Hedlund -
Robin -
Rui Nuno Capela -
v4hn