In snd's source tarball, there's a README.snd that has the following
answer:
Guile:
If you get a complaint along the lines of "ice-9/boot-9.scm not found",
it means you're running a version of Snd that has Guile loaded, but
Guile isn't installed locally. You need to install Guile. If Guile
is installed, try running 'guile-config info' to find out where it
thinks its boot files are. If you're using a prebuilt image from
ccrma-ftp, the relevant files should be in /usr/local/share/guile/1.4.
It's not impossible that running snd under strace would show you what the
actual desired path is. In the copious strace output, you should
be able to find lines like:
stat("/usr/local/share/guile/1.4/ice-9/boot-9.scm"...)
If you have installed Guile, but the snd image is looking in the wrong
place, try setting the envinronment variable GUILE_LOAD_PATH to the
correct directory:
setenv GUILE_LOAD_PATH /home/jimb/guile-snap
Another possibility is the %load-path variable; in your ~/.snd file try
something like:
(set! %load-path (cons "/home/bil/test" %load-path)))
(assuming you've put the guile files into /home/bil/test).
If the snd rpm process can't find the guile library, yet you have it
in /usr/local/lib, try the --nodeps switch to rpm (thanks to Charles
Waldman for this tip).
If the configure script says that your guile doesn't have
scm_make_smob_type, yet you do have guile 1.3.4 (or later) installed,
it's probably because the RedHat installer or someone, installed Guile
1.3 in /usr/bin and /usr/lib, but then the new version got installed
in /usr/local/bin. The simplest fix is to remove /usr/bin/guile and
/usr/bin/guile-config. If you get an inconsistent state here (that
is, configure thinks you're loading 1.3, but Snd itself finds 1.3.4),
you will get segfaults when the hooks are accessed (and probably
elsewhere). If you can run Snd at all, try snd --version -- this will
try to catch and report consistency problems.
If you're running linux-snd, you'll need guile 1.4 (it will appear
as libguile.so.8 in ldd).
> Other thing is that configure doesn't find guile-1.4.
> For some reason it thinks it's an older version and I have to manually
edit
> config.h
It's using guile-config to find guile; if you've got more
than one guile-config, it's up to your PATH setting, or
something, which one gets called. In Redhat, an ancient
version gets installed in /usr/bin, then if you install
your own using the defaults, it ends up in /usr/local/bin,
and in many cases, the new version is not noticed. You
could delete or rename /usr/bin/guile-config or change the
relevant environment variable. To see what configure sees,
in a shell try guile-config link or guile-config --version.
Fernando Lopez-Lezcano mentioned this possibility:
If you want to force a different guile do (if you're using bash):
PATH=/usr/marco/nicepath/bin/:$PATH ./configure --with-alsa --with-gtk
where /usr/marco/nicepath/bin is the path where the guile-config you
want
PATH=/usr/marco/nicepath/bin:$PATH make
On Tue, 17 Jul 2001, Expert wrote:
> Dang, snd does not do much, what do I do with this?
>
>
> [ntr@kittypuss ntr]$ snd
> ERROR: In procedure primitive-load-path:
> ERROR: Unable to find file "ice-9/boot-9.scm" in load path
> [ntr@kittypuss ntr]$
>
>
>
> On Tuesday 17 July 2001 02:51 pm, so spoke Laura Conrad:
> > >>>>> "expert" == expert <[EMAIL PROTECTED]> writes:
> >
> > expert> Does anyone know of sound editing software that does not
> > expert> suckfault like mixview or run poopy like SoundStudio?
> >
> > I use snd. Ecawave is probably good too, but can be a pain to install.
>
