Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Sat, 13 Oct 2001 13:28:29 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: problems compiling current cygwin cvs release Message-ID: <20011013132829.A31163@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <005a01c153be$743de6b0$fd1c440a AT BRAMSCHE> <20011013130856 DOT A29865 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011013130856.A29865@redhat.com> User-Agent: Mutt/1.3.21i 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/ > libiberty/ # This is the "target" libiberty used by winsup > newlib/ > winsup/ cgf