17 Sep
2004
17 Sep
'04
1:12 a.m.
Hi,
I'm trying to follow Dave's instructions for building fst-1.6
http://www.djcj.org/LAU/quicktoots/toots/vst-plugins/
at the section called "Building and Installing the fst System" on my
Gentoo laptop. Here's wht I'm doing:
flash VST $ tar xvfz fst-1.6.tar.gz
flash VST $ cd fst-1.6
flash fst-1.6 $ mkdir vst
flash fst-1.6 $ cd vst
flash vst $ cp /home/mark/vstsdk/vstsdk2.3/source/common/aeffectx.h .
flash vst $ cp /home/mark/vstsdk/vstsdk2.3/source/common/AEffect.h .
flash vst $ cd ..
flash fst-1.6 $ ./fixheaders
sed: can't read aeffectx.h: No such file or directory
flash fst-1.6 $ cd vst/
flash vst $ ../fixheaders
flash vst $ cd ..
flash fst-1.6 $ ./autogen.sh
flash fst-1.6 $ ./configure
<SNIP>
config.status: creating fst/Makefile
config.status: creating fst/include/config.h
Configure finished. Do 'make' to build the project.
flash fst-1.6 $ make
<SNIP>
gcc -c -I. -Iinclude -I/usr/include/wine/windows/..
-I/usr/include/wine/windows/../.. -I/usr/include/wine/windows -g -O2
-fPIC -I .. -I./vst -DDLLPATH=\"/usr/lib/wine\"
-DLIBPATH=\"/usr/local/lib\" -D_REENTRANT -o fstconfig.o fstconfig.c
gcc -o fstconfig fstconfig.o -L. -lfst
make[1]: Leaving directory `/home/mark/data/VST/fst-1.6/fst'
flash fst-1.6 $ su -
Password:
root@flash ~ # cd ~mark/data/VST/fst-1.6
root@flash /home/mark/data/VST/fst-1.6 # make install
/bin/sh ./mkinstalldirs /usr/local/lib/pkgconfig
./mkinstalldirs: ./mkinstalldirs: No such file or directory
make: *** [install-pkgconfigDATA] Error 127
root@flash /home/mark/data/VST/fst-1.6 #
Can anyone tell what I'm doing wrong here?
There is the one mistake in the instructions on the QuickToot page where
it seems to tell me to run fixheaders from the wrong place, but I
haven't figured out how to get past this.
I was able to build fst-1.5 quite awhile agio but of course have
forgotten the trick.
Thanks,
Mark
17 Sep
17 Sep
2:14 a.m.
On Fri, Sep 17, 2004 at 12:55:40PM EST, Mark Knecht wrote:
Hi,
I'm trying to follow Dave's instructions for building fst-1.6
http://www.djcj.org/LAU/quicktoots/toots/vst-plugins/
at the section called "Building and Installing the fst System" on my
Gentoo laptop. Here's wht I'm doing:
<Snip>
flash fst-1.6 $ make
<SNIP>
gcc -c -I. -Iinclude -I/usr/include/wine/windows/..
-I/usr/include/wine/windows/../.. -I/usr/include/wine/windows -g -O2
-fPIC -I .. -I./vst -DDLLPATH=\"/usr/lib/wine\"
-DLIBPATH=\"/usr/local/lib\" -D_REENTRANT -o fstconfig.o fstconfig.c
gcc -o fstconfig fstconfig.o -L. -lfst
make[1]: Leaving directory `/home/mark/data/VST/fst-1.6/fst'
flash fst-1.6 $ su -
Password:
root@flash ~ # cd ~mark/data/VST/fst-1.6
root@flash /home/mark/data/VST/fst-1.6 # make install
/bin/sh ./mkinstalldirs /usr/local/lib/pkgconfig
./mkinstalldirs: ./mkinstalldirs: No such file or directory
make: *** [install-pkgconfigDATA] Error 127
root@flash /home/mark/data/VST/fst-1.6 #
The mkinstalldirs file in the tarball is missing. Either grab this file from
another file, or search through your autoconf files for a copy of this file.
found in /usr/share/automake-ver where ver is the version of automake you
have installed.
There is the one mistake in the instructions on the
QuickToot page where
it seems to tell me to run fixheaders from the wrong place, but I
haven't figured out how to get past this.
You need to get the vst header files, and put them in the vst subdirectory
of the tarball. Then from the vst directory, run ../fixheaders. However, there
is more you have to do to the headers. I am not at my audio box right now, and
can't remember off the top of my head.
--
Luke Yelavich
http://www.audioslack.com
luke(a)audioslack.com
11:36 a.m.
Greetings:
All of this points up why I wish the tutorials were wiki-ized. The fst
1.6 package has not been repaired, even though I sent a notice to the
developers quite some time ago. I certainly deplore the existence of
misleading information as much as anyone else, but I simply can't keep
up with things like this anymore.
I'm sorry for wasting your time, Mark, and I hope you get things
operational despite my instructions. ;) I know how it feels: yesterday
I spent an hour compiling xine for my laptop, only to find that the UI
wouldn't build unless I used a newer version of the library. Grrr...
Luke, if you or anyone else can supply me with updated
compile/installation/configuration details for libfst or the vstserver
I'll do one more update on the tutorial. Please try to point out where
my tutorial is failing for you and I'll make the necessary changes.
Best regards,
dp
Luke Yelavich wrote:
On Fri, Sep 17, 2004 at 12:55:40PM EST, Mark Knecht
wrote:
Hi,
I'm trying to follow Dave's instructions for building fst-1.6
http://www.djcj.org/LAU/quicktoots/toots/vst-plugins/
at the section called "Building and Installing the fst System" on my
Gentoo laptop. Here's wht I'm doing:
<Snip>
flash fst-1.6 $ make
<SNIP>
gcc -c -I. -Iinclude -I/usr/include/wine/windows/..
-I/usr/include/wine/windows/../.. -I/usr/include/wine/windows -g -O2
-fPIC -I .. -I./vst -DDLLPATH=\"/usr/lib/wine\"
-DLIBPATH=\"/usr/local/lib\" -D_REENTRANT -o fstconfig.o fstconfig.c
gcc -o fstconfig fstconfig.o -L. -lfst
make[1]: Leaving directory `/home/mark/data/VST/fst-1.6/fst'
flash fst-1.6 $ su -
Password:
root@flash ~ # cd ~mark/data/VST/fst-1.6
root@flash /home/mark/data/VST/fst-1.6 # make install
/bin/sh ./mkinstalldirs /usr/local/lib/pkgconfig
./mkinstalldirs: ./mkinstalldirs: No such file or directory
make: *** [install-pkgconfigDATA] Error 127
root@flash /home/mark/data/VST/fst-1.6 #
The mkinstalldirs file in the tarball is missing. Either grab this file from
another file, or search through your autoconf files for a copy of this file.
found in /usr/share/automake-ver where ver is the version of automake you
have installed.
There is the one mistake in the instructions on
the QuickToot page where
it seems to tell me to run fixheaders from the wrong place, but I
haven't figured out how to get past this.
You need to get the vst header files, and put them in the vst subdirectory
of the tarball. Then from the vst directory, run ../fixheaders. However, there
is more you have to do to the headers. I am not at my audio box right now, and
can't remember off the top of my head.
11:56 a.m.
Dave Phillips wrote:
Greetings:
All of this points up why I wish the tutorials were wiki-ized. The fst
1.6 package has not been repaired, even though I sent a notice to the
developers quite some time ago. I certainly deplore the existence of
misleading information as much as anyone else, but I simply can't keep
up with things like this anymore.
Don't worry about it too much I'll first try to implement Luke's
instructions for fixing this or I'll drop back to fst_1.5.
I'm sorry for wasting your time, Mark, and I hope you get things
operational despite my instructions. ;) I know how it feels: yesterday
I spent an hour compiling xine for my laptop, only to find that the UI
wouldn't build unless I used a newer version of the library. Grrr...
Yesterday was no worse than others. The instructions were actually VERY
helpful. My only input was on the fixheaders step change the instructions to
cd vst
../fixheaders
cd ..
and that will be taken care of. This step was documented in some other
readme file somewhere.
BTW - How could I ever get disappointed with you for all the great stuff
you put on the web?!?! You're stuff is, overall, really amazing. I'd be
lost without it! Where the real responsibility lies, looking at the
software IP products my company delivers as a model, is with the
developers and packagers. Everyone includes a README. Some include an
INSTALL. In many/most cases they seem to go out unmodified from Gnu and
cause more wasted time than help. Cheers to all the developers that
write their own README and INSTALL docs and make this work better.
Luke, if you or anyone else can supply me with updated
compile/installation/configuration details for libfst or the vstserver
I'll do one more update on the tutorial. Please try to point out where
my tutorial is failing for you and I'll make the necessary changes.
Best regards,
dp
Luke Yelavich wrote:
On Fri, Sep 17, 2004 at 12:55:40PM EST, Mark
Knecht wrote:
Hi,
I'm trying to follow Dave's instructions for building fst-1.6
http://www.djcj.org/LAU/quicktoots/toots/vst-plugins/
at the section called "Building and Installing the fst System" on my
Gentoo laptop. Here's wht I'm doing:
<Snip>
flash fst-1.6 $ make
<SNIP>
gcc -c -I. -Iinclude -I/usr/include/wine/windows/..
-I/usr/include/wine/windows/../.. -I/usr/include/wine/windows -g -O2
-fPIC -I .. -I./vst -DDLLPATH=\"/usr/lib/wine\"
-DLIBPATH=\"/usr/local/lib\" -D_REENTRANT -o fstconfig.o fstconfig.c
gcc -o fstconfig fstconfig.o -L. -lfst make[1]: Leaving directory
`/home/mark/data/VST/fst-1.6/fst'
flash fst-1.6 $ su -
Password: root@flash ~ # cd ~mark/data/VST/fst-1.6
root@flash /home/mark/data/VST/fst-1.6 # make install
/bin/sh ./mkinstalldirs /usr/local/lib/pkgconfig
./mkinstalldirs: ./mkinstalldirs: No such file or directory
make: *** [install-pkgconfigDATA] Error 127
root@flash /home/mark/data/VST/fst-1.6 #
The mkinstalldirs file in the tarball is missing. Either grab this
file from
another file, or search through your autoconf files for a copy of this
file.
found in /usr/share/automake-ver where ver is the version of automake you
have installed.
There is the one mistake in the instructions on
the QuickToot page where
it seems to tell me to run fixheaders from the wrong place, but I
haven't figured out how to get past this.
You need to get the vst header files, and put them in the vst
subdirectory
of the tarball. Then from the vst directory, run ../fixheaders.
However, there
is more you have to do to the headers. I am not at my audio box right
now, and
can't remember off the top of my head.
1:01 p.m.
Mark Knecht wrote:
Don't worry about it too much I'll first try
to implement Luke's
instructions for fixing this or I'll drop back to fst_1.5.
I've updated the tutorial and sent it to Patrick. Hopefully the
corrected version will be on-line asap.
Yesterday was no worse than others. The instructions
were actually
VERY helpful. My only input was on the fixheaders step change the
instructions to
cd vst
../fixheaders
cd ..
and that will be taken care of. This step was documented in some other
readme file somewhere.
I've always run fixheaders from the top-level directory by using
'./fixheaders' but the tutorial didn't make that clear. However, I've
followed your practice and indicated that the user should cd to the
fst-x.x/vst directory and run '../fixheaders'. That should resolve that
difficulty. Btw, I've not had to do anything more to those files, so I'm
not sure what further fixes Luke has in mind.
I've also added a note about the missing mkinstalldirs and how to link
or copy it.
Best,
dp
9:02 p.m.
On Sat, Sep 18, 2004 at 01:37:14AM EST, Dave Phillips wrote:
I've always run fixheaders from the top-level
directory by using
'./fixheaders' but the tutorial didn't make that clear. However, I've
followed your practice and indicated that the user should cd to the
fst-x.x/vst directory and run '../fixheaders'. That should resolve that
difficulty. Btw, I've not had to do anything more to those files, so I'm
not sure what further fixes Luke has in mind.
When I built fst, I only had to run the fixheaders script. However, when I tried
to build Jack fst, the build failed due to errors in one of the header files.
I was using the latest SDK from Steinberg at the time. I remember being able to
make a small modification to the header file, and fst built successfully,
although I never managed to get it running.
--
Luke Yelavich
http://www.audioslack.com
luke(a)audioslack.com
9:25 p.m.
Luke Yelavich wrote:
On Sat, Sep 18, 2004 at 01:37:14AM EST, Dave Phillips
wrote:
Luke,
I had the same problems. Workign offline with some of the developers
they sent me the modified aeffectx.h file which allowed me to get
jack_fst to build. However right now it won't run due to some old wine
stuff being installed in the wrong area.
I have a bad habbit of pulling the compile trigger rather quickly.
It's just code. It should work. Right? If it doesn't no harm done. Right?
Wrong. I had Ardour working with VST plugin support just yesterday,
but discovered while talking to las and essej that all on of the stuff I
built by hand I never used the --prefix=/usr option so everything was in
/usr/local. I made a decision to clean that up. So far I have pretty
much all of the stuff rebuit - wine, fst, jack_fst, ardour and I don't
know how many other things, but unfortunately I'm having one continueing
problem. When I try to run jack_fst it ends up complaining about not
being able to find a file in /usr/local/lib, so womewher out there on my
system there are still remnents of the old setup.
Now my job is essentially search and destroy...
I will get this done...I will get this done...I will...
Thanks for your help and support!
Cheers,
Mark
I've always run fixheaders from the top-level
directory by using
'./fixheaders' but the tutorial didn't make that clear. However, I've
followed your practice and indicated that the user should cd to the
fst-x.x/vst directory and run '../fixheaders'. That should resolve that
difficulty. Btw, I've not had to do anything more to those files, so I'm
not sure what further fixes Luke has in mind.
When I built fst, I only had to run the fixheaders script. However, when I tried
to build Jack fst, the build failed due to errors in one of the header files.
I was using the latest SDK from Steinberg at the time. I remember being able to
make a small modification to the header file, and fst built successfully,
although I never managed to get it running.
9:51 p.m.
On Sat, Sep 18, 2004 at 09:08:05AM EST, Mark Knecht wrote:
Luke,
I had the same problems. Workign offline with some of the developers
they sent me the modified aeffectx.h file which allowed me to get
jack_fst to build. However right now it won't run due to some old wine
stuff being installed in the wrong area.
What modifications need to be made to this file as well as the fixheaders stuff?
I want to see whether those changes are the same the ones I made.
--
Luke Yelavich
http://www.audioslack.com
luke(a)audioslack.com
19 Sep
19 Sep
8:37 p.m.
Dave Phillips wrote:
Greetings:
All of this points up why I wish the tutorials were wiki-ized. The fst
1.6 package has not been repaired, even though I sent a notice to the
developers quite some time ago. I certainly deplore the existence of
misleading information as much as anyone else, but I simply can't keep
up with things like this anymore.
I'm sorry for wasting your time, Mark, and I hope you get things
operational despite my instructions. ;) I know how it feels: yesterday
I spent an hour compiling xine for my laptop, only to find that the UI
wouldn't build unless I used a newer version of the library. Grrr...
Luke, if you or anyone else can supply me with updated
compile/installation/configuration details for libfst or the vstserver
I'll do one more update on the tutorial. Please try to point out where
my tutorial is failing for you and I'll make the necessary changes.
Best regards,
dp
But in the end Dave, and will significant kind help from the guys on the
Ardour-Dev chat server, I now have the full version of NI's Battery
working under jack_fst-1.2/fst_1.6/wine-20040505 and it works perfectly
as far as I can tell. It hasn't crashed on my once in a few hours of
using it. The GUI seems perfect. sound it great. Hooks up to Rosegarden
and the timing seems good to me. (Not that much testing, but come
certainly.)
The only problem I had was that for some reason the second disk, which
contains all the drum kits, reads in correupted files on my Linux box.
The CD is fine itself. I took the files in question, saved them on a
windows machine, and then wrote a new CD. That CD copied just fine.
This is NOT a copy protected CD so it's nothing like that. It just
doesn't read correctly and puts corrupted files on my drive. Strange...
Very cool to be able to run this run drum sampler on my Linux box!
I entered it on Tim's Linux VST site.
cheers,
Mark
17 Sep
17 Sep
12:56 p.m.
Luke Yelavich wrote:
Yes - your instructions were correct, and this is what I was doing.
My comment was more that Dave's instructions didn't tell you to cd to
vst before doing ../fixheaders. That's all.
So I now have 1.6 built (I guess...) and I'll see if I can get
jack_fst and Ardour rebuilt to take advantage of this.
Cheers,
Mark
The mkinstalldirs file in the tarball is missing. Either grab this file from
another file, or search through your autoconf files for a copy of this file.
found in /usr/share/automake-ver where ver is the version of automake you
have installed.
Luke,
First, thanks for the help. It's working now. I wouldn't have gotten
there without your inputs.
Now, I was not able to quite understand what you meant above but,
since fst_1.5 works and fst_1.6 doesn't, I thought I'd find a copy of
mkinstalldirs in the fst_1.5 directory somewhere and get that. I was
surprised to find that it wasn't there either.
I then did a compare of the two Makefiles and it turned out that the
fst_1.6 Makefile had two extra lines in it concerning mkinstalldirs. As
an experiment I commented one out and moved the other since a comment
seemed to upset vim. Now fst_1.6 builds!
I do not understand how fst_1.5 and fst_1.6 really generate these
Makefiles but clearly there are differences.
There is the one mistake in the instructions on
the QuickToot page where
it seems to tell me to run fixheaders from the wrong place, but I
haven't figured out how to get past this.
You need to get the vst header files, and put them in the vst subdirectory
of the tarball. Then from the vst directory, run ../fixheaders. However, there
is more you have to do to the headers. I am not at my audio box right now, and
can't remember off the top of my head.
7399
days inactive
7402
days old
linux-audio-user@lists.linuxaudio.org
9 comments
4 participants
participants (4)
-
Dave Phillips -
Luke Yelavich -
Mark Knecht -
Mark Knecht