next install roadblock
Steve Petersen
spetey@umich.edu
Fri, 03 Aug 2001 00:28:12 -0400
"Michael T. Garrison Stuber" wrote:
>
> > I could only decipher references to slib, so I installed
> > 'slib-2d2-1.noarch.rpm' in hopes that might help. I also found the file
> > slib/require.scm it wanted in /usr/share/umb-scheme/slib/require.scm.
> > So I symbolically linked to it in '/usr/local/share/guile' and in '.',
> > where it seemed to be looking, but no luck--got the same error.
>
> Guile needs the whole slib, not just require.scm. Thus, your symlink
> intuition is correct, you just need to create it differently. Go into
> /usr/local/share/guile and create a symbolib link called slib to the
> /usr/share/umb-scheme/slib directory. I do not claim to understand the
> inner workings of guile, but I know this is what my system requires. You
> may also need to set your SCHEME_LIBRARY_PATH. On my system the RPM adds a
> script to /etc/profile.d to do this for you.
Thanks again for the help; just the simlink seems to work. The *next*
inscrutable (for me) roadblock to g-wrap's configuring:
----------------------------------------------------
:
:
Making all in test
make[2]: Entering directory `/tmp/g-wrap-1.1.9/test'
/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..
-O2 -Werror -Wall -g
-I../libruntime-guile -g -O2 -I/usr/local/include -c gw-test-parent.c
rm -f .libs/gw-test-parent.lo
gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -Werror -Wall -g
-I../libruntime-guile -g -O2 -I/usr/local/include -c
-fPIC -DPIC gw-test-parent.c -o .libs/gw-test-parent.lo
cc1: warnings being treated as errors
gw-test-parent.c: In function `gw_init_module_gw_test_parent':
gw-test-parent.c:167: warning: implicit declaration of function `strcmp'
make[2]: *** [gw-test-parent.lo] Error 1
make[2]: Leaving directory `/tmp/g-wrap-1.1.9/test'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/g-wrap-1.1.9'
make: *** [all-recursive-am] Error 2
----------------------------------------------------
Again, sorry to tire all of you with a layperson's attempt--but it may
give you programmers some insight into what we ignorati are up against.
Some 6-8 tricky package installations down the road, I'm at least more
than half-way toward actually running gnucash, right?!
Thanks again,
Steve