Rich Felker

Can you check the `config.log` in the libstdc++ build dir to see if it looks like it did anything weird here?

I don't see anything wrong from config.log...

Uhg, does it somehow not know how to do atomics on baseline arm (linux kuser_helper)?

This is a real bug in upstream GCC that we should patch. I'm not sure when I'll get to it, but here's a note to self to do it. By...

I'm pretty sure the gcc 4.2.1 support is just bitrotted; it probably needs to be removed. But I'll take a closer look.

Most fundamentally, this is a non-starter without musl supporting an i386-softfloat ABI. The normal i386 ABI uses an x87 register for floating point returns, so there's no way to do...

If you're just testing and plan to add the fpu emulation later, I'd just test with programs that don't use floating point, or under a kernel that traps the exception...

Can you provide more information about what you're asking for? Surely `TARGET=armv5-linux-musleabi` already works. Is "te" some incompatible variant, or...?

Not in particular, but it's just part of a general principle of not hiding visual progress indication. I just measured and the time difference is miniscule here, 29.0s vs 27.7s....

Do you still believe this is an issue needing action from the musl-cross-make side? I'm closing old issues and would like to close this if not.