unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: lloda <lloda@sarc.name>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Unable to build Guile on macOS
Date: Fri, 9 Apr 2021 09:27:56 +0200	[thread overview]
Message-ID: <393A9752-CD13-4DCC-ADBA-950933737AE1@sarc.name> (raw)
In-Reply-To: <CA+XASoW7Xki2RC28u87MzhoABnnonuG-w_4=0A_JT1ROGTFb+w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]



> On 9 Apr 2021, at 00:10, Aleix Conchillo Flaqué <aconchillo@gmail.com> wrote:
> 
> On Thu, Apr 8, 2021 at 1:10 PM lloda <lloda@sarc.name> wrote:
>> 
>> 
>> 
>>> On 8 Apr 2021, at 06:43, Aleix Conchillo Flaqué <aconchillo@gmail.com> wrote:
>>> 
>>> The following recent Gnulib commit fixes the issue:
>>> 
>>> https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=fc6d7d850bdebfed81e9212910f44edf99dd7743
>>> 
>>> If someone could update Gnulib to a more recent version I'd really
>>> appreciate it.
>>> 
>>> Thanks!
>>> 
>>> Aleix
>> 
>> I pushed an update to branch wip-gnulib-update. Could you give that a try? I tested on macos 10.15.7 and I had two test failures, in async.test and filesys.test, but I'm not sure those didn't happen before.  (Everything was fine on Debian).
>> 
> 
> It builds fine now on macOS 11.2.3. I'm getting 2 errors as well (I
> don't see async.test though):
> 
> FAIL: 00-socket.test: setsockopt AF_INET: IPPROTO_TCP TCP_NODELAY
> FAIL: filesys.test: mkdtemp: invalid template
> 
> 
> Totals for this test run:
> passes:                 44240
> failures:               2
> unexpected passes:      0
> expected failures:      24
> unresolved test cases:  70
> untested test cases:    1
> unsupported test cases: 1
> errors:                 0
> 
> FAIL: check-guile
> ==================================
> 1 of 1 test failed
> Please report to bug-guile@gnu.org
> ==================================


Thanks for checking, for the record, this is what I got myself:

FAIL: 00-socket.test: setsockopt AF_INET: IPPROTO_TCP TCP_NODELAY

ERROR: asyncs.test: preemption via sigprof - arguments: ((wrong-type-arg #f "Wrong type (expecting ~A): ~S" ("resumable continuation" #<vm-continuation 1094b94e0>) (#<vm-continuation 1094b94e0>)))

FAIL: filesys.test: mkdtemp: invalid template

Totals for this test run:
passes:                 44240
failures:               2
unexpected passes:      0
expected failures:      24
unresolved test cases:  69
untested test cases:    1
unsupported test cases: 1
errors:                 1

Regards

	Daniel




[-- Attachment #2: Type: text/html, Size: 7739 bytes --]

      reply	other threads:[~2021-04-09  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  6:25 Unable to build Guile on macOS Aleix Conchillo Flaqué
2021-04-08  4:43 ` Aleix Conchillo Flaqué
2021-04-08 20:10   ` lloda
2021-04-08 22:10     ` Aleix Conchillo Flaqué
2021-04-09  7:27       ` lloda [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=393A9752-CD13-4DCC-ADBA-950933737AE1@sarc.name \
    --to=lloda@sarc.name \
    --cc=aconchillo@gmail.com \
    --cc=guile-devel@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).