i'm testing the glibc binary against the pr that adds it to run the native backend tests and was able to reproduce more of the behavior we're seeing in travis (where it needs `crti.o`/etc). it's clear we're going to need to make some edits to the glibc release sources and makefiles before compiling them. we can do this with

sed

now, but i was wondering if it would make more sense to maintain a github fork of the glibc git and key into the SHA of that repo, because the automated edits may break in future releases.

is there an explanation somewhere for why we're bringing along glibc?