From: Greg Troxel <gdt@lexort.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: mmap for guile
Date: Tue, 05 Jul 2022 08:49:48 -0400 [thread overview]
Message-ID: <rmih73vvi4z.fsf@s1.lexort.com> (raw)
In-Reply-To: 87fsjg8x2a.fsf@gnu.org
[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Greg Troxel <gdt@lexort.com> skribis:
>
>> I have been meaning to try to build this under NetBSD, to check
>> portability. I think the mmap code should by default rely only on what
>> POSIX guarantees:
>> https://pubs.opengroup.org/onlinepubs/9699919799/functions/mmap.html
>
> Agreed.
Great to hear that. There are a bunch of guile fans in BSD-land and we
try to keep up :-) After I wrote, I actually did get to testing on
netbsd-9 amd64, which was easier than I thought it might be. With the
patch Matt sent, guile 3.0.8 built (and packaged under pkgsrc), and I
was able to see the mmap functions docs in the repl.
I tried to run the tests but got an undefined symbol, not apparently
related. My machine is in the process of rebuilding most packages and I
will revist when that's done, starting with tests on unmodified 3.0.8.
>> As for referring to glibc, that reference only resolves on GNU/Linux
>> systems, whereas any POSIX system ought to have an mmap man page, so it
>> would be nice not to drop the man page ref, esp. as it grounds the
>> implementation as being about the POSIX interface.
>
> The manual can mention the man page too, sure, but note that the manual
> already refers to glibc’s for all things libc.
I see -- I guess there is a fine line between glibc the implementation
of what C99/POSIX defines as "what must be in libc" the spec, but that's
a big can of worms and if this documentation ends up like the existing
one, then it is not reasonable for me to worry about it :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2022-07-05 12:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 15:37 mmap for guile Matt Wette
2022-06-26 16:21 ` Matt Wette
2022-06-26 17:06 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-06-26 18:11 ` Maxime Devos
2022-07-04 10:09 ` Ludovic Courtès
2022-07-04 13:14 ` Greg Troxel
2022-07-04 20:03 ` Ludovic Courtès
2022-07-05 12:49 ` Greg Troxel [this message]
2022-07-19 13:20 ` Maxime Devos
2022-07-21 9:14 ` Ludovic Courtès
2022-07-19 13:30 ` Maxime Devos
2022-07-19 13:34 ` Maxime Devos
2022-06-26 18:21 ` Maxime Devos
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=rmih73vvi4z.fsf@s1.lexort.com \
--to=gdt@lexort.com \
--cc=guile-devel@gnu.org \
--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).