On Tue, 2011-05-17 at 12:48 -0400, DJ Delorie wrote: > > 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. >
And the problem is that libiberty is assuming that it *knows* what functions newlib provides, so that it doesn't need to check directly. This is just broken... # If we are being configured for newlib, we know which functions # newlib provide and which ones we will be expected to provide.
