Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3C1F3614.1080300@fnxweb.com>
Date: Tue, 18 Dec 2001 12:27:00 +0000
From: Neil Bird <neil AT fnxweb DOT com>
Reply-To: Cygwin <cygwin AT sources DOT redhat DOT com>
Organization: Thales Sensors  (but only on behalf of myself)
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.6) Gecko/20011121
X-Accept-Language: en-us
MIME-Version: 1.0
To: Cygwin <cygwin AT sources DOT redhat DOT com>
Subject: Random 'Signal 11' during configure/make [of gcc]
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


   I have need to prove that I can compile up a gcc 2.95.3 with 
the latest libstdc++ (to get the proper C++ STL).

   I've set up cygwin as best as seems necessary, and fetched 
the latest gcc & libstdc++ source (gcc from the cygwin src dist.).


   However, whenever I do a 'configure' in a clean directory, I 
get random 'Signal 11' (seg. viol.?) messages come up, mostly in 
the checking phase, but occasionally also in the 
Makefile-generation phase at the end.

   They don't appear to happen in the same place each time.

   Typically, though, a 'strace -f' gave me a 246Mb output with 
/no/ 'signal 11's at all :-/

   After that seeming success, I'm doing a make, but I can see 
the signals happening there occasionally again, so I don't hold 
out much hope of a working build.

   Any ideas?


   FWIW, this is on NT; I installed Cygwin onto a network drive, 
but then put it onto my C: drive in case that was the problem; 
I'm currently running with '/' mounted off the network 
(primarily for the /etc changes I made initially), but pretty 
well everything else from the local install.

   I don't think my attempted insertion of the 2.95.3-compat. 
new libstdc++ has any bearing on the problem.

-- 
[neil AT fnx ~]# rm -f .signature
[neil AT fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil AT fnx ~]# exit


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/