From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7197 invoked by alias); 28 Aug 2007 09:32:07 -0000 Received: (qmail 9242 invoked by uid 22791); 28 Aug 2007 08:50:28 -0000 X-Spam-Check-By: sourceware.org Message-ID: <46D3E1CA.9030700@emcraft.com> Date: Tue, 28 Aug 2007 09:32:00 -0000 From: Sergei Poselenov User-Agent: Thunderbird 1.5.0.7 (X11/20061008) MIME-Version: 1.0 To: gsl-discuss@sources.redhat.com Subject: Re: Failure building GSL-1.9 on FPU-less powerpc References: <46CD3DF1.9000605@emcraft.com> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -101.4 (---------------------------------------------------) Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00019.txt.bz2 Hello Brian, Brian Gough wrote: > At Thu, 23 Aug 2007 11:57:37 +0400, > Sergei Poselenov wrote: >> Investigation shows that the problem is that the "configure" >> script chose the "gnuppc" IEEE arithmetic interface type by default, >> which assume the FPU is present on the target and included >> fp-gnuppc.c into the build. >> >> Then the compilation failed because fp-gnuppc.c tries to operate >> the FPU hardware constants from fpu_control.h for FPU-aware >> powerpcs; these constants are absent on my system. >> >> How can I build GSL? > > You can comment out the HAVE_GNUPPC_IEEE_INTERFACE line in config.h to > disable that part. > Yes, thank you for the hint, I've finally came to something similar - set "ac_cv_c_ieee_interface" to "no" prior to running "configure". This selected "#include fp-gnuc99.c" in fp.c with HAVE_DECL_FEENABLEEXCEPT defined on my system. Don't you think the system-wide fpu-control.h for fpu-less systems should have _FPU_RC_NEAREST and others defined for compatibility? They already have there: #define _FPU_GETCW(cw) 0 #define _FPU_SETCW(cw) do { } while (0) Regards, Sergei