From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 60971@debbugs.gnu.org, lloda <lloda@sarc.name>,
"guile-devel@gnu.org" <guile-devel@gnu.org>,
Greg Troxel <gdt@lexort.com>
Subject: bug#60971: GNU Guile 3.0.9rc1 available for testing!
Date: Mon, 23 Jan 2023 10:47:48 -0800 [thread overview]
Message-ID: <CA+XASoUiq47d8veK_nkB-pOOwgoe3V-bypath0RnddqmLpMrMg__15181.557931804$1674499764$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <87h6wh34t0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
On Mon, Jan 23, 2023 at 2:48 AM Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> Greg Troxel <gdt@lexort.com> skribis:
>
> > lloda <lloda@sarc.name> writes:
> >
> >> This looks like https://debbugs.gnu.org/60971 <
> https://debbugs.gnu.org/60971> on mac os.
> >
> > Yes, it does.
> >
> > My quick reaction is that if the POSIX-required macros operation on
> > system types that might be struct, then faking up ints for testing is
> > unsound.
> >
> > Maybe only do verify if guile has to define macros, and don't try to
> > test the OS?
>
> So something like the patch below?
>
Oh, I missed the other report. Yes, this works on macOS as just reported by
Daniel. No other issues.
Aleix
[-- Attachment #2: Type: text/html, Size: 1706 bytes --]
next prev parent reply other threads:[~2023-01-23 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v8l15hb2.fsf@inria.fr>
[not found] ` <rmiy1pv48rj.fsf@s1.lexort.com>
[not found] ` <562CD6BE-42D3-4D4C-AB4C-2B4A5341F525@sarc.name>
[not found] ` <rmiy1pu3a7e.fsf@s1.lexort.com>
2023-01-23 10:48 ` bug#60971: GNU Guile 3.0.9rc1 available for testing! Ludovic Courtès
[not found] ` <87h6wh34t0.fsf@gnu.org>
2023-01-23 18:04 ` lloda
2023-01-23 18:47 ` Aleix Conchillo Flaqué [this message]
[not found] ` <079E639D-3A09-48E6-AAE1-913896DC692E@sarc.name>
2023-01-23 21:59 ` bug#60971: build failure of v3.0.9rc1 on mac os 12.6 Ludovic Courtès
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='CA+XASoUiq47d8veK_nkB-pOOwgoe3V-bypath0RnddqmLpMrMg__15181.557931804$1674499764$gmane$org@mail.gmail.com' \
--to=aconchillo@gmail.com \
--cc=60971@debbugs.gnu.org \
--cc=gdt@lexort.com \
--cc=guile-devel@gnu.org \
--cc=lloda@sarc.name \
--cc=ludo@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).