Vladimir Panteleev

> Yes, it would break compiling on systems that dont't have >=glibc-2.34 which was released in august 2021. But won't this make it impossible to also *run* D programs on...

> I don't understand what you refer to. phobos isn't backward abi compatible so the changes here would affect only programs written in the future. `closefrom` is only available in...

> Therefore the bindings D uses to the libc headers provided by the host should match the definitions for that host. But that's not relevant, is it? D does not...

> What are the headers in `core.sys.*` for then? If they're meant to only represent the functions that are available in a libc implementation in an arbitrarily (but consistent) range...

> This is because, when building my program I built it against the glibc version on my machine. > > ... > > Here's what I get if I try...

> I have already pointed out that you cannot use dlsym at all, period, end of story, no ifs ands or buts. We already use it to load libcurl at...

> The D binary tarballs don't avoid any particular problem by being built against an older glibc -- the D binary tarballs simply do the correct thing, which all software...

Unfortunately no, they are an indication that something went wrong with the rebase.

It seems to be due to a bug in nixpkgs. The bug manifests with the nixpkgs version in `flake.lock`, but not a more recent version.

``` 2dcae7d82f5ef0b373413d2fbfc1001141561c74 is the first good commit commit 2dcae7d82f5ef0b373413d2fbfc1001141561c74 Author: pennae Date: Sat Dec 25 15:20:26 2021 +0100 lib/attrsets: use builtins.zipAttrsWith if available lib/attrsets.nix | 3 ++- 1 file changed,...