brian-brt

I threw up my fork in 8b06fed3b6a6559b24fc0e5c43ad51f200562825. As mentioned in the commit message, it's a combination of the things I mentioned here and some hacks that don't make sense to...

> Thanks! > > Some misc notes: > > * I mentioned target triples / Bazel platforms because [`extra_targets`, user configurable toolchains, and wasm support #85](https://github.com/grailbio/bazel-toolchain/pull/85) tries to [add the...

> > That's neat, and I agree it's somewhat excessive. I think it's unlikely that a toolchain for some untested platform will work without tweaking, so I'd rather prioritize making...

> Do the tarballs you're using for `aarch64`/`x86` linux sysroots use glibc? Yep. They're built by just merging the data tarballs of .deb files Debian/Ubuntu (I've done it with a...

@rrbutani thoughts on where to take this now? I think it makes sense to start with me pulling out the parts needed for cross compilation on top of the latest...

I guess getting libc++ from the sysroot works. My approach gets it from the Clang release for the target architecture, which means less things to configure in the sysroot but...