On Wed, Aug 6, 2014 at 1:29 AM, Warren Young <[email protected]> wrote:
> That has more to do with contemporaneity. When you talk about Linux 3.x,
> you also necessarily imply recent versions of glibc and such, which is the
> true dependency.
>
+1
> I seriously doubt Fossil actually makes any syscalls added to Linux 3.x,
> not present in Linux 2.6. (If there are any such calls, they're probably
> nonportable.)
>
Correct. The only system-level APIs we use anywhere (off the top of my
head):
- networking, but those are standard APIs which don't randomly change from
glibc version A to B.
- system(), fork(), exec(), but those are also age-old and don't just
randomly change.
- Windows and (IIRC) Mac: native-to/from-unicode string conversions ('Nix
platforms do not do these).
i'm pretty certain (not 100%) that that's it, but i know we don't use any
Linux-specific calls which might depend on a newer glibc version, except
possibly indirectly via the fuse module (its public API does not expose any
such dependencies, but it almost certainly has low-level deps on the OS).
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
