{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibpsixyuwgdw6f7qj6l6x2y7xyrgacva6xfkfnsqxvcd2ugdyoz6q",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3ml6ej6bc5hr2"
  },
  "path": "/t/pre-rfc-target-glibc-proposal-to-add-native-support-for-glibc-versions-for-the-gnu-targets/24225#post_7",
  "publishedAt": "2026-05-06T07:20:13.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "comex:\n\n> For a more substantive point: It’s odd that you propose two different ways to specify the glibc deployment target (triple suffix and `-C` argument), especially when they are both different from how Apple deployment targets are specified (environment variable).\n\nTriple suffix is to support the approach zig-build uses today, which should simplify migration. IMHO, the `-C target-glibc:X.Y` and the config file are the proper approach.\n\nAs you mentioned, the MacOS env variable is hacky, and I do not think that following that path is the right way to handle this feature.\n\n> In other words, I would suggest picking one new mechanism, and adding support for it for both glibc and Apple targets.\n\nMaking that change for Apple is a bit of a stretch for this RFC (and completely irrelevant for the stub libs part).",
  "title": "[Pre-RFC] target-glibc: Proposal to add native support for GLIBC versions for the -gnu targets"
}