Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 20 Oct 2000 15:58:10 -0400 Message-Id: <200010201958.PAA20122@envy.delorie.com> From: DJ Delorie To: cygwin AT sources DOT redhat DOT com In-reply-to: <20001020141055.B14647@redhat.com> (message from Christopher Faylor on Fri, 20 Oct 2000 14:10:55 -0400) Subject: Re: Cygwin SEGVs References: <20001017120354 DOT A9810 AT cygnus DOT com> <20001017205249 DOT 7782 DOT qmail AT lizard DOT curl DOT com> <20001020053504 DOT 5350 DOT qmail AT lizard DOT curl DOT com> <20001020135305 DOT C14359 AT cygnus DOT com> <200010201803 DOT OAA19313 AT envy DOT delorie DOT com> <20001020141055 DOT B14647 AT redhat DOT com> > Actually, I don't think it was you, DJ. I remember the discussion > to use any output at all from a compilation as indication of an > error. I think that is what changed, wasn't it? I thought that > Alexandre Oliva made this change. > > I know that you were trying valiantly to *fix* it, though. Alexandre and I were working together to come up with a suitable fix for the "big problem" (wrong things getting linked when building cygwin), which is when the additional -B option got added. It triggered the gcc message. I submitted the patch to get rid of the gcc message; Jeff Law applied it. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com