[EMAIL PROTECTED] (Paul Jarc) writes:
Building 1.6.5 fails for me:
[...]
Paul, any news on this front? Things like this are very hard to
reproduce on a second system, and everything seems to work fine for me
here...
However, there is one snag that I noticed: try changing the line in
Rob Browning [EMAIL PROTECTED] wrote:
It's not the PATH, that might be the problem. It's the lib dir. If
you have 1.6.4 installed in /usr/lib, then you'd need to actually
uninstall it to test.
Ah. Everything is installed in its own directory here, and there even
is no /usr/lib or /lib
Rob Browning [EMAIL PROTECTED] wrote:
Just out of curiousity, do you have a version of guile already
installed on that machine in the default path, and if so (and if it's
easy), are the results any different if you remove that copy of guile
(including libs) and clean/re-build 1.6.5?
I do have
[EMAIL PROTECTED] (Paul Jarc) writes:
Rob Browning [EMAIL PROTECTED] wrote:
Just out of curiousity, do you have a version of guile already
installed on that machine in the default path, and if so (and if it's
easy), are the results any different if you remove that copy of guile
(including
Building 1.6.5 fails for me:
...
creating guile
cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc
continuations.doc debug.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc
eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc gc.doc goops.doc
[EMAIL PROTECTED] (Paul Jarc) writes:
Building 1.6.5 fails for me:
...
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/fs/home/mount/home/prj/src/spf/guile-1.6.5'
make: *** [all] Error 2
I can work around it by setting
LD_LIBRARY_PATH=$PWD/libguile-ltdl/.libs.
I've seen
