This is the mail archive of the
mailing list for the GCC project.
Re: Version 1.126 of libstdc++-v3/configure.in broke pre-installednewlib builds
> What does libiberty do? I'm not quite sure what to do, and kind of think
> that the current configure is mostly correct (but there should be a way
> for you to get a cross compiler with an installed newlib working. (Maybe
> --with-sysroot=foo would work.)
> It would be nice if libiberty and libstdc++ did the same thing, wouldn't
libiberty is built before newlib, so it can't autodetect anything
anyway. It has a list of which targets use newlib and which don't in
its configury, and for the ones that don't (and can't be
autodetected), it explicitly lists which functions are needed.
One idea is to extract this info somehow, into a separate file in
libiberty, so that other target libraries can use it. Since libiberty
is used in many projects, I don't think it makes sense to put the list