From: Tobias Gerdin <tgerdin@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org
Subject: Re: project: translate guile-tutorial.texi to use guile-cairo
Date: Tue, 20 Sep 2011 21:19:42 +0200 [thread overview]
Message-ID: <CAJiKzQOzopcWxDaSJSR5+tPEKYM=kQ_CCOVc8qktfjautQVo2g@mail.gmail.com> (raw)
In-Reply-To: <CAJiKzQMmSpbkGeT-JuuVHOcrYQXKa0Hmp8T6-J7qz0g=vkf_3A@mail.gmail.com>
2011/9/20 Tobias Gerdin <tgerdin@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
next prev parent reply other threads:[~2011-09-20 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 9:51 project: translate guile-tutorial.texi to use guile-cairo Tobias Gerdin
2011-09-20 19:19 ` Tobias Gerdin [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-28 9:41 Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJiKzQOzopcWxDaSJSR5+tPEKYM=kQ_CCOVc8qktfjautQVo2g@mail.gmail.com' \
--to=tgerdin@gmail.com \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).