On Tue, Oct 18, 2011 at 9:49 AM, Roland McGrath <mcgra...@google.com> wrote: > When libiberty defines psignal, it doesn't use the canonical signature. > This came up as a problem in a configuration where libiberty wants to > define psignal itself, but the build environment's <signal.h> declares > it too. > > This was a --with-newlib configuration using the newlib trunk, where newlib > does define psignal (and strsignal, among other things), but libiberty's > configure thinks it knows exactly what newlib does and doesn't define > without checking. This hard-coding seems unwise to me, exactly because of > the potential for cases like this, where newlib's set of available > functions changes over time.
libiberty is no longer compiled for the target so this should never happen really. Thanks, Andrew Pinski
