On May 5 11:09, Ulrich Weigand wrote: > This list does not include psignal, which indeed newlib did not provide > -- until yesterday, when that patch was committed ... > > > I'm not quite sure how to fix this ... any suggestions? Did this problem > occur in the past when newlib was extended to provide some new function? > > I guess the immediate build problem will disappear once the libiberty > prototype is fixed to include const, but then we'll just have two copies > of psignal (one in newlib, one in libiberty), which may not be ideal > either.
Developers using libiberty don't have to use newlib so the definition in libiberty still makes sense, right? I don't know how to avoid this problem in configure, other than by adding AC_LIBOBJ([psignal]). Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat
