problems compiling current cygwin cvs release

[Ralf Habacker]

> On Sat, Oct 13, 2001 at 01:08:56PM -0400, Christopher Faylor wrote:
> >On Sat, Oct 13, 2001 at 10:10:00AM +0200, Ralf Habacker wrote:
> >>2. On linking the cygwin dll the following file is used from the libiberty:
> >>	/home/habacker/src/cvs.cygwin.com/build/libiberty/strsignal.o
> >>
> >>If one configure libiberty for using with ld the function strsignal()
> >>isn't defined, because configure finds a defined strsignal.  If
> >>libiberty is shared between cygwin an ld/binutils, than there is a
> >>problem.  ???
> >
> >Your build area is screwed up.  cygwin is not supposed to share a
> libiberty with
> >'ld'.  If you have cygwin in the same build area as 'ld' then the
> layout should
> >look something like this:
> >
> >build/
> >  bfd/
> >  binutils/
> >  ld/
>    libiberty/		# There is a libiberty here that 'ld' should be using
> >  i686-pc-cygwin/

Hmmh, i686-pc-cygwin is empty on my pc. the newlib an winsup dir are direct
under build

> >    libiberty/		# This is the "target" libiberty used by winsup
> >    newlib/
> >    winsup/
>
> cgf
>