14 Sep
2008
14 Sep
'08
7:07 p.m.
This one has me flummoxed, as it's turned out to be essentially
un-googlable:
In trying to get Rubber Band compiled on my new Kubuntu load, I ran
./configure with the settings to I found from before to ignore the Vamp
stuff:
-----
./configure Vamp_CFLAGS=no Vamp_LIBS=no
-----
Configure runs fine, everything checks out, then I run make, and get
this error:
-----
g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC
-Wall no -Irubberband -Isrc -c -o src/ConstantAudioCurve.o
src/ConstantAudioCurve.cpp
g++: no: No such file or directory
make: *** [src/ConstantAudioCurve.o] Error 1
-----
Searching for "g++: no: No such file or directory" turns up absolutely
nothing that helped. Maybe someone here can nudge me in the right
direction? Thanks!
Regards,
Darren Landrum
14 Sep
14 Sep
8:27 p.m.
On Sun, Sep 14, 2008 at 9:07 PM, Darren Landrum
<darren.landrum(a)sbcglobal.net> wrote:
This one has me flummoxed, as it's turned out to
be essentially
un-googlable:
In trying to get Rubber Band compiled on my new Kubuntu load, I ran
./configure with the settings to I found from before to ignore the Vamp
stuff:
-----
./configure Vamp_CFLAGS=no Vamp_LIBS=no
-----
Configure runs fine, everything checks out, then I run make, and get
this error:
-----
g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC
-Wall no -Irubberband -Isrc -c -o src/ConstantAudioCurve.o
src/ConstantAudioCurve.cpp
g++: no: No such file or directory
make: *** [src/ConstantAudioCurve.o] Error 1
-----
Searching for "g++: no: No such file or directory" turns up absolutely
nothing that helped. Maybe someone here can nudge me in the right
direction? Thanks!
Regards,
Darren Landrum
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
What is the output of 'which g++'?
It should show you where g++ is installed.
The error makes it look like g++ (the gcc c++ compiler) is not
installed on your system.
8:35 p.m.
Justin Smith wrote:
What is the output of 'which g++'?
It should show you where g++ is installed.
The error makes it look like g++ (the gcc c++ compiler) is not
installed on your system.
The output is:
darren@ashe:~/Downloads/rubberband-1.2$ which g++
/usr/bin/g++
So it is there. Just for kicks, though, I did "locate g++" and got:
darren@ashe:~/Downloads/rubberband-1.2$ locate g++
/usr/bin/g++
/usr/bin/g++-4.2
/usr/bin/x86_64-linux-gnu-g++
/usr/bin/x86_64-linux-gnu-g++-4.2
I don't know if that means anything. g++ is a symlink to g++-4.2, and
x86_64-linux-gnu-g++ is a symlink to x86_64-linux-gnu-g++-4.2.
Thanks!
Regards,
Darren Landrum
8:53 p.m.
On Sun, Sep 14, 2008 at 10:35 PM, Darren Landrum
<darren.landrum(a)sbcglobal.net> wrote:
Justin Smith wrote:
I did not look closely enough.
You set Vamp_CFLAGS to be 'no', so it adds 'no' to the command line
when compiling for vamp. g++ therefore says "no: no such file or
directory" because the command line is feeding it 'no' and so it
thinks 'no' is the name of a compilable file. Try configuring without
the Vamp_CFLAGS define.
What is the output of 'which g++'?
It should show you where g++ is installed.
The error makes it look like g++ (the gcc c++ compiler) is not
installed on your system.
The output is:
darren@ashe:~/Downloads/rubberband-1.2$ which g++
/usr/bin/g++
So it is there. Just for kicks, though, I did "locate g++" and got:
darren@ashe:~/Downloads/rubberband-1.2$ locate g++
/usr/bin/g++
/usr/bin/g++-4.2
/usr/bin/x86_64-linux-gnu-g++
/usr/bin/x86_64-linux-gnu-g++-4.2
I don't know if that means anything. g++ is a symlink to g++-4.2, and
x86_64-linux-gnu-g++ is a symlink to x86_64-linux-gnu-g++-4.2.
Thanks!
Regards,
Darren Landrum
9:12 p.m.
Justin Smith wrote:
I did not look closely enough.
You set Vamp_CFLAGS to be 'no', so it adds 'no' to the command line
when compiling for vamp. g++ therefore says "no: no such file or
directory" because the command line is feeding it 'no' and so it
thinks 'no' is the name of a compilable file. Try configuring without
the Vamp_CFLAGS define.
The thing is, that configure line worked perfectly back on Ubuntu
Studio. Now when I do this:
-----
darren@ashe:~/Downloads/rubberband-1.2$ ./configure Vamp_LIBS=no
-----
I get this error during config:
-----
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 idea is to compile without the Vamp examples.
Thanks again!
Regards,
Darren Landrum
15 Sep
15 Sep
8:57 a.m.
Quoting Darren Landrum <darren.landrum(a)sbcglobal.net>et>:
Justin Smith wrote:
It might have to do with your shell. I think bash can handle that kind
of environment assignment but the C-shells can't (btw are you sure you
didn't run "Vamp_LIBS=no ./configure" in UbuntuStudio. I think that's
the correct way).
Try running "export Vamp_LIBS=no" or "setenv Vamp_LIBS no" prior to
running a plain ./configure
/peder
I did not look closely enough.
You set Vamp_CFLAGS to be 'no', so it adds 'no' to the command line
when compiling for vamp. g++ therefore says "no: no such file or
directory" because the command line is feeding it 'no' and so it
thinks 'no' is the name of a compilable file. Try configuring without
the Vamp_CFLAGS define.
The thing is, that configure line worked perfectly back on Ubuntu
Studio. Now when I do this:
-----
darren@ashe:~/Downloads/rubberband-1.2$ ./configure Vamp_LIBS=no 
2:15 p.m.
On Sunday 14 September 2008, Darren Landrum wrote:
This one has me flummoxed, as it's turned out to
be essentially
un-googlable:
In trying to get Rubber Band compiled on my new Kubuntu load, I ran
./configure with the settings to I found from before to ignore the Vamp
stuff:
-----
./configure Vamp_CFLAGS=no Vamp_LIBS=no
-----
Configure runs fine, everything checks out, then I run make, and get
this error:
-----
g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC
-Wall no -Irubberband -Isrc -c -o src/ConstantAudioCurve.o
src/ConstantAudioCurve.cpp
g++: no: No such file or directory
make: *** [src/ConstantAudioCurve.o] Error 1
-----
Searching for "g++: no: No such file or directory" turns up absolutely
nothing that helped. Maybe someone here can nudge me in the right
direction? Thanks!
Well basically you tell the configure script to add a string "no" to every
build line.. Then of course g++ tries to compile a file called "no". Which is
probably not what you want..
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
5:35 p.m.
Florian Schmidt wrote:
Well basically you tell the configure script to add a
string "no" to every
build line.. Then of course g++ tries to compile a file called "no". Which is
probably not what you want..
So why did it work before? Some kind of environment difference?
If I want to tell configure not to compile any of the Vamp stuff, how
would I do it?
I ask not just because I want to avoid Vamp for now, but because my last
experience with compiling Vamp went very, very poorly. It was all
documented on this list.
Someway, somehow, I was once able to tell Rubber Band not to compile its
Vamp plug-in examples.
Thanks for the help.
Regards,
Darren Landrum
6:30 p.m.
Am Montag 15 September 2008 schrieb Darren Landrum:
Florian Schmidt wrote:
Are you really sure you used "no" as argument for these variables? they come
from pkgconfig usually and contain paths and/or options, or are empty if the
package in question isn't installed. Try
./configure Vamp_CFLAGS= Vamp_LIBS=
This seems to have the desired effect here, although Vamp is installed and
detected by ./configure, the g++ lines look like this later:
g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall
-Irubberband -Isrc -c -o src/AudioCurve.o src/AudioCurve.cpp
Well basically you tell the configure script to
add a string "no" to every
build line.. Then of course g++ tries to compile a file called "no". Which is
probably not what you want..
So why did it work before? Some kind of environment difference?
If I want to tell configure not to compile any of the Vamp stuff, how
would I do it?
I ask not just because I want to avoid Vamp for now, but because my last
experience with compiling Vamp went very, very poorly. It was all
documented on this list.
Someway, somehow, I was once able to tell Rubber Band not to compile its
Vamp plug-in examples.
Thanks for the help.
Regards,
Darren Landrum
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Edgar
7:12 p.m.
Edgar Aichinger wrote:
Am Montag 15 September 2008 schrieb Darren Landrum:
Are you really sure you used "no" as argument for these variables? they
come
Yes, as I copied and pasted the string I used right into the email I
sent to this list when I said "okay, it works now, this is what I did."
./configure Vamp_CFLAGS= Vamp_LIBS=
This still gives me the error that Vamp is not installed, so still a no-go.
Why is this such a problem? As far as I know, the dependency on Vamp is
only for some example Vamp plug-ins using Rubber Band that I don't want
anyway.
Regards,
Darren Landrum
5988
days inactive
5989
days old
linux-audio-user@lists.linuxaudio.org
9 comments
5 participants
participants (5)
-
Darren Landrum -
Edgar Aichinger -
Florian Schmidt -
Justin Smith -
Peder Hedlund