X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <85C4645B18FA4D37852D725436AB741B@desktop2>
References: <BANLkTi=ud0PMGwwzRRh+hvDVcv4=nACEYA@mail.gmail.com> <20110409160524.GA29135@ednor.casa.cgf.cx> <BANLkTikd0e3xrD_NS+HFbaSmwFd-YzkBLw@mail.gmail.com> <BANLkTi=LAnmGNaF-MXS5ZUp23TFq9rCDoA@mail.gmail.com> <BANLkTi=hGQXjiEa3s2HZW+yYfC9YSaXXaQ@mail.gmail.com> <85C4645B18FA4D37852D725436AB741B@desktop2>
From: Hugh Myers <hsmyers@gmail.com>
Date: Sun, 10 Apr 2011 04:47:37 -0600
Message-ID: <BANLkTi=XbmP=4PaC6e6_Lbe37r5C9hz5-Q@mail.gmail.com>
Subject: Re: newlib and long-double question
To: cygwin@cygwin.com
Cc: Sisyphus <sisyphus1@optusnet.com.au>,
        marco atzeri <marco.atzeri@gmail.com>, "N. C." <necrocowmoo@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

The OP is trying to build Perl itself, not use it; hence the need for
long double support functions...

--hsm

On Sun, Apr 10, 2011 at 4:25 AM, Sisyphus <sisyphus1@optusnet.com.au> wrote:
>
> ----- Original Message ----- From: "marco atzeri"
>
>>> On a Linux system that I have access to, I see that those functions
>>> are in /lib/libm.* but cygwin's /lib/libm.* still seems to lack them.
>>> Is there any work around or alternate version ofthis lib that actually
>>> has these functions. I honestly do not mean to be rude, but how
>>> difficult is it to impliment these functions which seem so common in
>>> most unix-like systems?
>>
>> It is not overcomplicated to implement it, but it takes time and
>> someone to do it.
>> When I implemented all the complex functions (cabs, ccos..) I spent one
>> month
>> to make it right. A more capable guy will take less surely, but as
>> mention I see little
>> benefit moving from 64 to 80 bits so I was not interested to implement i=
t.
>>
>
> I sense an opportunity here to plug (to the op) the Math::MPFR perl modul=
e -
> for which the gmp and mpfr C libraries are required.
> I guess one could also use Math::BigFloat, but I assume the op has already
> considered (and rejected) that option - the performance hit incurred by i=
ts
> use has always discouraged me.
> Perhaps he has also already considered and rejected Math::MPFR, but it se=
ems
> to me to be by far the best option for achieving added precision with
> floating point numbers - at least until such time as building perl with
> -Duselongdouble has been facilitated.
>
> Cheers,
> Rob
>
>
>
> --
> Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html
> FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/
> Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html
> Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple
>
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

