unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 32677@debbugs.gnu.org
Subject: bug#32677: Installation of guile-debbugs fails
Date: Tue, 11 Sep 2018 09:40:39 +0200	[thread overview]
Message-ID: <877ejs5vns.fsf@gmx.de> (raw)
In-Reply-To: <87a7opkot6.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 10 Sep 2018 23:47:17 +0200")

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi Michael,

Hi Ricardo,

>>> ./configure has failed. I think you are missing guile-2.2. Could you try
>>> again with guile installed?
>>
>> --8<---------------cut here---------------start------------->8---
>> [albinus@BRONB4NHFYN1 ~]$ which guile
>> /usr/bin/guile
>> [albinus@BRONB4NHFYN1 ~]$ guile --version
>> guile (GNU Guile) 2.0.14
>> --8<---------------cut here---------------end--------------->8---

Meanwhile, I've changed to another machine running Ubuntu 18.04. It has
installed guile 2.2:

--8<---------------cut here---------------start------------->8---
detlef:~/src/guile-debbugs> which guile
/usr/bin/guile
detlef:~/src/guile-debbugs> /usr/bin/guile --version
guile (GNU Guile) 2.2.3
--8<---------------cut here---------------end--------------->8---

>> Furthermore, a syntax error seems to tell something different. If it is
>> really true that guile 2.2 is missing, I would expect a respective error
>> message.
>
> Do you have pkg-config installed?  GUILE_PKG is a macro that depends on
> macros provided by pkg-config.

Yes, it is:

--8<---------------cut here---------------start------------->8---
detlef:~/src/guile-debbugs> which pkg-config
/usr/bin/pkg-config
detlef:~/src/guile-debbugs> /usr/bin/pkg-config --version
0.29.1
--8<---------------cut here---------------end--------------->8---

And still the same error:

--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---

> Ricardo

Best regards, Michael.





  reply	other threads:[~2018-09-11  7:40 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 [this message]
2018-10-16 16:34         ` Arun Isaac
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=877ejs5vns.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=32677@debbugs.gnu.org \
    --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).