From: alex sassmannshausen <alex.sassmannshausen@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: Re: guile-hall issues converting my project to a hall project
Date: Thu, 18 Feb 2021 13:18:38 +0100 [thread overview]
Message-ID: <CAKdwf2DYXr05gA4BPqmPvLBNM4LmTZUjWqpmDwvJvtsKDmK5jA@mail.gmail.com> (raw)
In-Reply-To: <YC2c9e3JJqbPoOwG@lepton>
Yes, I forgot to mention this in my wall of text. Vladimir's solution is
correct.
Hall does this in master too.
Alex
On Wed, 17 Feb 2021, 23:47 Vladimir Zhbanov, <vzhbanov@gmail.com> wrote:
>
> Hi Zelphir,
>
> On Tue, Feb 16, 2021 at 01:23:34AM +0100, Zelphir Kaltstahl wrote:
> ...
>
> > The line in the generated `configure` file looks quite simple. It is
> only:
> >
> > ~~~~
> > GUILE_PKG(3.0 2.2 2.0)
> > ~~~~
>
> > It looks like there could be a simple fix, but I do not know what to do
> > about this error and how that error could happen in the first place.
>
> IIUC, the macro args should be in square brackets:
>
> GUILE_PKG([3.0 2.2 2.0])
>
> --
> Vladimir
>
>
next prev parent reply other threads:[~2021-02-18 12:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 21:49 guile-hall issues converting my project to a hall project Zelphir Kaltstahl
2021-02-07 9:14 ` tomas
2021-02-07 13:30 ` Tim Van den Langenbergh
2021-02-11 20:30 ` Zelphir Kaltstahl
2021-02-16 0:23 ` Zelphir Kaltstahl
2021-02-17 22:47 ` Vladimir Zhbanov
2021-02-18 12:18 ` alex sassmannshausen [this message]
[not found] ` <11206998.46ALo4VoAQ@terra>
[not found] ` <02902ff9-1585-a453-4e36-c9a731eee6fe@posteo.de>
2021-02-16 16:48 ` Tim Van den Langenbergh
2021-02-16 18:12 ` Zelphir Kaltstahl
2021-02-17 21:17 ` Alex Sassmannshausen
2021-02-18 19:16 ` Zelphir Kaltstahl
2021-02-21 13:42 ` Alex Sassmannshausen
2021-02-22 11:34 ` guile-hall packaging guide Zelphir Kaltstahl
2021-02-22 20:52 ` Jérémy Korwin-Zmijowski
2021-02-23 16:32 ` Alex Sassmannshausen
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=CAKdwf2DYXr05gA4BPqmPvLBNM4LmTZUjWqpmDwvJvtsKDmK5jA@mail.gmail.com \
--to=alex.sassmannshausen@gmail.com \
--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).