Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Can't build the latest snapshot with gcc-2.95.2-1. References: <20000518135101 DOT A14123 AT cygnus DOT com> <200005181810 DOT OAA25203 AT envy DOT delorie DOT com> <20000518141549 DOT A14536 AT cygnus DOT com> <20000518144025 DOT A15811 AT cygnus DOT com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 19 May 2000 04:41:30 +0900 In-Reply-To: Chris Faylor's message of Thu, 18 May 2000 14:40:25 -0400 Message-ID: Lines: 21 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Thu, 18 May 2000 14:40:25 -0400 >>> Chris Faylor said: > I've checked in changes to cygwin/winsup and cygwin/utils which > eliminate the necessity of including "winsup.h". Hopefully, this > will nuke this problem. I can still observe the same problem. "mount.cc" didn't take part in the problem. The problem is that any application can't be compiled with the latest snapshot because of the unresolved reference in "libcygwin.a". According to the explanation by Mumit, the problem is triggered by the sigthread::init(). This inlined method introduces the reference to the destructor into all source codes which include "sigproc.h". The reference only in "libccrt0.o" can't be resolved and causes the problem. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology