Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 2 Mar 2005 15:37:42 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: loading of wsock32 disturbs FPU Message-ID: <20050302143742.GZ18314@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <200503021306.32969.r.schulz@dkfz.de> <20050302143149.GA3187@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050302143149.GA3187@cygbert.vinschen.de> User-Agent: Mutt/1.4.2i On Mar 2 15:31, Corinna Vinschen wrote: > On Mar 2 13:33, Dave Korn wrote: > > Hm. We probably need to put a finit instruction into the autoload code > > somewhere. wsock_init () looks like just the place...... now if I just > > persuade the CVS code to build without a SIG11 (grmbl grmbl....) > > Hmm? -v please. I just added an finit call to wsock_init and it seems to work fine. Are there any non-FPU CPUs >= i386 out there which would choke on this machine instruction? I guess not, but I'm not exactly fluent in ix86 history... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/