Well, I shouldn't since autoconf should deal with it automatically. I
remember I did this just because of a workaround, at that time Guile-2.2
has issue to detect the correct version number, and I was hurry to release.
Long time ago, I forget to remove it.
Best regards
On Thu, Jan 9, 2020, 02:24
On Wed, Jan 08 2020, Nala Ginrut wrote:
> Finally I found the problem is that I left a m4/guile.m4 in Artanis for
> some reasons. It's solved by remove it.
>
> Thanks for all the helps!
>
> Best regards
>
> On Mon, Jan 6, 2020 at 2:56 PM Nala Ginrut wrote:
I am far from an expert at Autoconf, an
Finally I found the problem is that I left a m4/guile.m4 in Artanis for
some reasons. It's solved by remove it.
Thanks for all the helps!
Best regards
On Mon, Jan 6, 2020 at 2:56 PM Nala Ginrut wrote:
> Hi Matt!
> Thanks for the help.
> However, it seems doesn't work for me. I think your solut
Hi Matt!
Thanks for the help.
However, it seems doesn't work for me. I think your solution is to solve
mixed guile version detection issue, right?
I'm building it in docker, a pure clean Debian10 environment. Hmm...
On Sat, Jan 4, 2020 at 7:29 AM Matt Wette wrote:
>
>
> On 1/3/20 10:44 AM, Matt
On 1/3/20 10:44 AM, Matt Wette wrote:
On 1/3/20 6:53 AM, Matt Wette wrote:
I am running into other issues, however, when there is a
guile in my path that appears before anything else, but a guile-2
that appears from another directory. I am working to add
--with-guile to fix that. I'm hav
On 1/3/20 6:53 AM, Matt Wette wrote:
I am running into other issues, however, when there is a
guile in my path that appears before anything else, but a guile-2
that appears from another directory. I am working to add
--with-guile to fix that. I'm having problems checking against
2.0.14, for
