From: rvclayton@acm.org (R. Clayton)
To: guile-user@gnu.org
Subject: guile-www install.
Date: Thu, 26 Nov 2009 19:53:46 -0500 [thread overview]
Message-ID: <87r5rk4wkl.fsf@UlanBator.myhome.westell.com> (raw)
I installed guile on a debian testing system:
$ dpkg -l guile*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
un guile <none> (no description available)
ii guile-1.8 1.8.7+1-2 The GNU extension language and Scheme interp
ii guile-1.8-doc 1.8.7+1-2 Documentation for Guile 1.8
un guile-1.8-doc- <none> (no description available)
ii guile-1.8-libs 1.8.7+1-2 Main Guile libraries
$
and then I wanted to install guile-www 2.26 (the latest, I believe), but ran
into this:
ul pwd
/usr/local/src/guile-www-2.26
$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for guile... /usr/bin/guile
checking for guile-config... no
configure: error: guile-config required but not found
$
Peeking ahead in configure, it seems it will also die when it looks for
guile-tools.
$ locate guile-config
$ locate guile-tools
$
This suggests that something is out of whack, but I don't know (apart from the
obvious) what it might be. What's the explanation, and the fix?
next reply other threads:[~2009-11-27 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 0:53 R. Clayton [this message]
2009-11-27 1:13 ` guile-www install Antonio P. P. Almeida
2009-11-27 1:20 ` Antonio P. P. Almeida
2009-11-27 1:20 ` Antonio P. P. Almeida
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=87r5rk4wkl.fsf@UlanBator.myhome.westell.com \
--to=rvclayton@acm.org \
--cc=guile-user@gnu.org \
/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).