From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: finding Guile
Date: Mon, 21 Jan 2019 09:18:46 +0000 [thread overview]
Message-ID: <87zhrufjwp.fsf@gmail.com> (raw)
In-Reply-To: <CA+XASoXfvRxRK9DUHsRKu6np1mwQ01R44wq_UxUFXrKe0uHqiA@mail.gmail.com>
Hi Aleix,
Thank you very much for contributing to this conversation. I feel this
is indeed the correct approach to solving this problem — Guile Hall
relies on the full autotools infrastructure to manage projects. I want
it to just use the guile.m4 provided by Guile, rather than maintaining
my own.
I will add my voice to seeing if we can get that patch merged into Guile
Core.
In order to support Ubuntu & potentially other distributions whilst the
patch is not yet merged, I will temporarily add a guile.m4 generator in
Hall.
Cheers,
Alex
Aleix Conchillo Flaqué writes:
> On Fri, Jan 18, 2019 at 12:49 AM Catonano <catonano@gmail.com> wrote:
>>
>> I opened a new ticket on the guile-hall repo
>> https://gitlab.com/a-sassmannshausen/guile-hall/issues/4
>>
>> I remind everybody that guile-hall is an attempt to create a command to
>> create and manage Guile based projects instrumented with the Autotools
>>
>> I found a symptom but I can't properly diagnose the cause.
>>
>> Maybe Alex already knows how to fix this. I opened it right now
>>
>> But I'd appreciate any help
>>
>
> I added a comment to the issue. I sent a patch to fix this in December.
>
> http://lists.gnu.org/archive/html/guile-devel/2018-12/msg00002.html
>
> Not sure who needs to accept it or when it will be accepted.
>
> Hope this helps.
>
> Aleix
prev parent reply other threads:[~2019-01-21 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 8:48 finding Guile Catonano
2019-01-20 4:37 ` Aleix Conchillo Flaqué
2019-01-21 9:18 ` Alex Sassmannshausen [this message]
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=87zhrufjwp.fsf@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--cc=aconchillo@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).