Dan Albert

> the new thing here is really "we tried to build a bunch of random stuff that we didn't historically". The new part is "and it broke". _We_ haven't been...

>> The new part is "and it broke". We haven't been building those things, but other people have. > > it seems highly unlikely that none of our existing polyfills...

It's probably both, but I think you're right that gnulib is a big part of it. That's also the one where I'm not sure there are going to be simple...

Getting from that page to the relevant headers isn't great either. Maybe we should start generating that page from the version scripts or something... Tbh it's a good argument for...

> It is due to the NDK using internal linkage inside c headers https://cs.android.com/android/platform/superproject/main/+/main:bionic/libc/include/sys/cdefs.h;l=262-268;drc=ed2d3832bd8afef5021c3efc6db3352f2b35a848 says they have to be. Unless @enh-google knows otherwise, this is something that'd have to be...

I'm waiting to hear back from someone in Android that should know more, but is this actually a problem? Where's it documented that the loop must exit immediately?

We're working on getting the infrastructure we need to ship NDK stuff in androidx. Unplanned doesn't mean never, just that I don't know when yet :) I'll being going through...

I haven't heard of that error before. Maybe @pirama-arumuga-nainar has? Given that it's a toolchain crash that was introduced in r23, it'd also be worth trying your code with the...

I don't think the presubmit builds are downloadable by non googlers, but https://android-review.googlesource.com/c/platform/ndk/+/1839724 updates to a newer LLVM. I've only lightly tested it but all our tests _build_ fine and...

> If you can smuggle a macOS (or even Linux) build to me, I could test it with our codebase and give you feedback That'd be paragraph 2 :) It'll...