From: Arun Isaac <arunisaac@systemreboot.net>
To: Michael Albinus <michael.albinus@gmx.de>,
Ricardo Wurmus <rekado@elephly.net>
Cc: 32677@debbugs.gnu.org
Subject: bug#32677: Installation of guile-debbugs fails
Date: Tue, 16 Oct 2018 22:04:53 +0530 [thread overview]
Message-ID: <cu78t2xzw7m.fsf@systemreboot.net> (raw)
In-Reply-To: <877ejs5vns.fsf@gmx.de>
> --8<---------------cut here---------------start------------->8---
> detlef:~/src/guile-debbugs> ./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 make supports nested variables... yes
> checking whether make supports nested variables... (cached) yes
> ./configure: line 2364: syntax error near unexpected token `2.2'
> ./configure: line 2364: `GUILE_PKG(2.2)'
> --8<---------------cut here---------------end--------------->8---
A minor update. I was able to reproduce this problem in a Guix
environment. If I install guile in the environment, this problem does
not manifest. If I don't have guile in the environment, this problem
manifests.
In other words, with
guix environment --ad-hoc guile autoconf automake pkg-config
this problem does not manifest. But, with
guix environment --ad-hoc autoconf automake pkg-config
this problem manifests. I have no idea why this is the case, but perhaps
this could be a lead worth investigating.
next prev parent reply other threads:[~2018-10-16 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 8:29 bug#32677: Installation of guile-debbugs fails Michael Albinus
2018-09-10 10:25 ` Arun Isaac
2018-09-10 10:59 ` Michael Albinus
2018-09-10 21:47 ` Ricardo Wurmus
2018-09-11 7:40 ` Michael Albinus
2018-10-16 16:34 ` Arun Isaac [this message]
2018-10-16 19:13 ` Ricardo Wurmus
2018-10-16 20:01 ` Arun Isaac
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=cu78t2xzw7m.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=32677@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=rekado@elephly.net \
/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).