From: Farid Zakaria <farid.m.zakaria@gmail.com>
To: libc-help@sourceware.org
Subject: assistance patching glibc for getprotobyname
Date: Wed, 30 Jun 2021 10:49:01 -0700 [thread overview]
Message-ID: <CACCo2jkTwe4ecw_OngtXjGAt4CgUBy-pi=caOT_sd35H8vuWjQ@mail.gmail.com> (raw)
Hello,
I'm trying to investigate a patch to glibc for the purpose of
http://nixos.org/ similar to what they have already accomplished for
the locales [1]
The goal is to patch glibc for _getprotobyname_ so that if an
environment variable is set, it will treat the environment variable
path as the database file.
The goal here for nixpkgs, is to have packages which are hermetic and
sealed -- depend on no external dependency. The issue at the moment is
that /etc/protocols must exist on the system which breaks the closure.
I've been trying to dig into the nss/ folder & codebase, but it's
heavy use of macros makes it difficult for me to determine some of the
scalpel cuts I need to perform.
I was hoping someone could point me at some breadcrumbs to start my edits.
[1] https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/glibc/nix-locale-archive.patch
Thank you.
Farid Zakaria
reply other threads:[~2021-06-30 17:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACCo2jkTwe4ecw_OngtXjGAt4CgUBy-pi=caOT_sd35H8vuWjQ@mail.gmail.com' \
--to=farid.m.zakaria@gmail.com \
--cc=libc-help@sourceware.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).