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 From: "Ralf Habacker" To: Subject: RE: problems compiling current cygwin cvs release Date: Sun, 14 Oct 2001 21:04:37 +0200 Message-ID: <007d01c154e3$11fbab60$fd1c440a@BRAMSCHE> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <20011013132829.A31163@redhat.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 > 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 >