From: Marco Atzeri <marco_atzeri@yahoo.it>
To: cygwin@cygwin.com
Subject: R: gfortran 4.3.4: NINT() intrinsic triggers undefined references to '_llround' and '_llroundf'
Date: Sat, 16 Oct 2010 05:38:00 -0000 [thread overview]
Message-ID: <250085.68907.qm@web25501.mail.ukl.yahoo.com> (raw)
In-Reply-To: <AANLkTimru_XVCwHrUsVUgbLfE7MjzO68NzA_14aUCWxZ@mail.gmail.com>
--- Ven 15/10/10, Cornelis de Gier ha scritto:
> The NINT() intrinsic in current
> gfortran under current cygwin triggers
> undefined references to '_llround' and '_llroundf'. I found
> a somewhat
> related post here:
> http://sourceware.org/ml/cygwin/2010-06/msg00369.html ,
> but I could
> not deduce a solution from this message.
>
> Below follows a small test program and the output of
> gfortran. The
> test program worked OK on a linux system.)
> ====================
> program testnint
> integer, parameter :: kr64 = selected_real_kind(15,307)
> integer, parameter :: ki64 = selected_int_kind(18)
>
> real(kr64)::dp=1.
> real::r=2.
>
> write(*,*),nint(r,ki64)
> write(*,*),nint(dp,ki64)
>
> endprogram testnint
> ====================
> $ gfortran -Wall testnint.f90
> /tmp/ccqOJVB5.o:testnint.f90:(.text+0x5c): undefined
> reference to `_llroundf'
> /tmp/ccqOJVB5.o:testnint.f90:(.text+0xd1): undefined
> reference to `_llround'
> collect2: ld returned 1 exit status
> ====================
>
>
> Cornelis
>
As Dave wrote the problem is inside cygwin
> I thought it was just because we are failing to export
> them in the cygwin.din file. The correct .o files are
> compiled as part of the newlib libm build.
but we forgot to make a patch.
I will look on it.
Marco
--
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
next prev parent reply other threads:[~2010-10-16 5:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 20:58 Cornelis de Gier
2010-10-16 5:38 ` Marco Atzeri [this message]
2010-10-16 12:12 ` Cornelis de Gier
2010-10-16 15:11 ` Marco Atzeri
2010-10-18 15:46 ` R: " Marco Atzeri
2010-10-19 11:56 ` Cornelis de Gier
2010-10-19 13:18 ` Marco Atzeri
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=250085.68907.qm@web25501.mail.ukl.yahoo.com \
--to=marco_atzeri@yahoo.it \
--cc=cygwin@cygwin.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).