public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Poselenov <sposelenov@emcraft.com>
To: gsl-discuss@sources.redhat.com
Subject: Re: Failure building GSL-1.9 on FPU-less powerpc
Date: Tue, 28 Aug 2007 09:32:00 -0000	[thread overview]
Message-ID: <46D3E1CA.9030700@emcraft.com> (raw)
In-Reply-To: <m33ay4pulu.wl%bjg@network-theory.co.uk>

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

  reply	other threads:[~2007-08-28  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 11:03 Sergei Poselenov
2007-08-27 21:26 ` Brian Gough
2007-08-28  9:32   ` Sergei Poselenov [this message]
2007-08-30 19:59     ` Brian Gough

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46D3E1CA.9030700@emcraft.com \
    --to=sposelenov@emcraft.com \
    --cc=gsl-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).