public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47032] libgfortran references complex long double functions missing on AIX
Date: Tue, 21 Dec 2010 18:37:00 -0000 [thread overview]
Message-ID: <bug-47032-4-nZSOvvOIxB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47032-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47032
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2010-12-21 18:37:21 UTC ---
On Tue, Dec 21, 2010 at 05:07:53PM +0000, dje at gcc dot gnu.org wrote:
> This is an interaction / assumption problem between the target (AIX) and
> libgfortran. libgfortran previously built with GCC 4.4 s, this is a regression
> because libgfortran is relying on more OS features without providing an
> alternative. And disabling all long double support (which works in G++) or
> disabling libgfortran on AIX because of this issue seems like a bad options.
>
libgfortran/configure.ac has lines of the form (note I wrapped the line)
AC_CHECK_LIB([m],[copysignl],[AC_DEFINE([HAVE_COPYSIGNL],[1],\
[libm includes copysignl])])
So, configure is already checking if libm contains the
the "long double functions". The problem appears to be
that AC_CHECK_LIB is a compile only test, and these tests
appear to pass on AIX. AIX rquires a link time test to
either unseti, e.g., HAVE_COPYSIGNL or configure in general
should do a link time tests instead of a compile time tests
to ensure the HAVE_* macros are unset.
next prev parent reply other threads:[~2010-12-21 18:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 16:22 [Bug libfortran/47032] New: " dje at gcc dot gnu.org
2010-12-21 16:42 ` [Bug target/47032] " kargl at gcc dot gnu.org
2010-12-21 17:08 ` dje at gcc dot gnu.org
2010-12-21 18:37 ` sgk at troutmask dot apl.washington.edu [this message]
2010-12-28 16:10 ` rguenth at gcc dot gnu.org
2011-01-06 19:15 ` dje at gcc dot gnu.org
2011-01-25 20:34 ` michael.haubenwallner at salomon dot at
2011-02-04 5:16 ` rwild at gcc dot gnu.org
2011-02-08 20:49 ` pogma at gcc dot gnu.org
2011-02-08 20:55 ` sgk at troutmask dot apl.washington.edu
2011-02-08 21:04 ` pogma at gcc dot gnu.org
2011-02-08 22:24 ` michael.haubenwallner at salomon dot at
2011-02-12 15:08 ` burnus at gcc dot gnu.org
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=bug-47032-4-nZSOvvOIxB@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).