14 Sep
2008
14 Sep
'08
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