newlib vs. libiberty mismatch breaks build (Re: [PATCH] Export psignal on all platforms)

Corinna Vinschen
Thu May 5 17:01:00 GMT 2011

On May  5 18:44, Ulrich Weigand wrote:
> DJ Delorie wrote:
> > > I don't know how to avoid this problem in configure, other than by adding
> > > AC_LIBOBJ([psignal]).
> > 
> > Right, the correct solution is - libiberty shouldn't provide psignal
> > if newlib does.  Making it match newlib is the wrong solution.
> I guess I agree, but the problem is exactly how to implement "if newlib
> does" ...  Usually, this would be a link test, which libiberty configure
> deliberately avoids for cross-builds, so it hardcodes "what newlib does".
> Do you suggest we should do the link test after all, or make the hard-
> coded newlib capability list somehow dynamic (depending on what)?
> Maybe I'm missing something, but I don't understand the AC_LIBOBJ suggestion.

Sorry about that.  I guess that should have been something along the
lines of

  AC_DEFINE(HAVE_PSIGNAL,1,[Define if you have psignal])


Corinna Vinschen
Cygwin Project Co-Leader
Red Hat

More information about the Newlib mailing list