> What I don't understand is why the newlib change broke older compilers.
Older compilers have the older libiberty. At the moment, libiberty cannot be built by *any* released gcc, because you cannot *build* any released gcc, because it cannot build its target libiberty. > The function has been added to newlib and the definitions in newlib are > correct. "Correct" is irrelevent. They don't match libiberty, so the build breaks. > If this is refering to the fact that libiberty doesn't grok > automatically if a symbol has been added to newlib, then that's a > problem in libiberty, not in newlib. It's a problem in every released gcc at the moment, so no released gcc can be built for a newlib target, without hacking the sources. > Otherwise, if you're building an older compiler, just use an older > newlib as well. The only option here is to not release a newlib at all until a fixed gcc release happens, then, and require that fixed gcc for that version of newlib forward.
