2011/9/20 Tobias Gerdin <tger...@gmail.com>:
> Lastly, just thought I'd mention an issue that I ran into when
> building Guile-Cairo (commit 1918626 from Git, looks like it
> corresponds to 1.9.91). When I run autogen/configure it complains that
> I need to supply a prefix argument because "the default prefix,
> /usr/local, is not in the default guile load path." But on my system
> it is, I built Guile from stable-2.0 branch and installed into the
> default /usr/local, so I do not think I should be seeing this error
> (it works if I supply --prefix=/usr/local to Guile-Cairo configure).
This would be a possible fix that WFM, but too hackish? But is there
no standard robust method for doing this? Will not all Guile libraries
need to solve this problem?
-Tobias
diff --git a/configure.ac b/configure.ac
index df7a306..eb90bea 100644
--- a/configure.ac
+++ b/configure.ac
@@ -34,7 +34,7 @@ AC_PROG_CC
AC_STDC_HEADERS
AC_PROG_LIBTOOL
-if test "x$prefix" = xNONE; then
+if test "x$prefix" = xNONE -a `guile-config info prefix` != "/usr/local"; then
AC_MSG_ERROR([No explicit prefix given.
Guile-Cairo requires you to explicitly enter in a prefix when
