> On Apr 8, 2024, at 10:48 AM, Eric Wong <e...@80x24.org> wrote: > >> I’m not enough of a Perl person to fully untangle this. As >> best I can tell, the intent is that non-Linux/BSD OSes should >> still work with Inline::C, but this doesn’t work in practice >> due to a bug? > > Right. Patch below should fix it, test feedback appreciated.
From a quick test, it seems to work: public-inbox-httpd starts and is happy to serve up an archive. Thanks for the quick fix! >> It may also be possible to use the BSD approach on Darwin - >> Darwin ascribes to the BSD school of thought where libc is the >> only Officially Stable interface, but if you can get away with >> it on the real BSDs maybe you can get away with it on fake BSD >> too. > > NetBSD and FreeBSD both document the underlying syscall numbers > remain stable (but not the name => number mapping). OpenBSD has > no stable numbering, but goes as far as to patch Perl to route > the `syscall' perlop through their libc to avoid breaking Perl > scripts. > > I have no idea if Darwin maintains any stability guarantees at > all like the above OSes, so Inline::C may be safer, here. Indeed, Apple explicitly doesn’t make such a guarantee: https://developer.apple.com/forums/thread/706419 So Inline::C is definitely the move. > -------8<------- > Subject: [PATCH] syscall: set default constants for Inline::C platforms > > This ought to fix compile errors on platforms we don't > explicitly support. > > Reported-by: Gaelan Steele <gael...@icloud.com> Ah, that’s the wrong email address. (My fault! My mail client has an unfortunate default I haven’t figured out how to change, and I forgot to set it before sending this time.) Would it be possible to use this one (g...@canishe.com <mailto:g...@canishe.com>) instead? Best wishes, Gaelan
