public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/33583] FAIL: gfortran.dg/gamma_1.f90
Date: Mon, 26 Nov 2007 17:42:00 -0000 [thread overview]
Message-ID: <20071126174251.14875.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33583-276@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from burnus at gcc dot gnu dot org 2007-11-26 17:42 -------
(In reply to comment #10)
> Bug 33942 was marked as a duplicate of this one, but it is not fixed
Can you enlighten us what is missing? As a configure test was added, it should
have found the lgamma function of "libm" and for gamma it should use the one
provided by libgfortran.
Do you get linker errors? Or what exactly is the error message/problem?
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33583
next prev parent reply other threads:[~2007-11-26 17:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 23:13 [Bug libfortran/33583] New: " danglin at gcc dot gnu dot org
2007-09-29 12:45 ` [Bug libfortran/33583] " rguenth at gcc dot gnu dot org
2007-09-29 16:15 ` dave at hiauly1 dot hia dot nrc dot ca
2007-09-29 16:47 ` dave at hiauly1 dot hia dot nrc dot ca
2007-09-30 22:28 ` fxcoudert at gcc dot gnu dot org
2007-09-30 22:31 ` dave at hiauly1 dot hia dot nrc dot ca
2007-10-24 19:30 ` tkoenig at gcc dot gnu dot org
2007-10-30 10:36 ` fxcoudert at gcc dot gnu dot org
2007-11-16 22:32 ` fxcoudert at gcc dot gnu dot org
2007-11-16 22:46 ` fxcoudert at gcc dot gnu dot org
2007-11-16 22:46 ` fxcoudert at gcc dot gnu dot org
2007-11-26 17:18 ` michael dot a dot richmond at nasa dot gov
2007-11-26 17:42 ` burnus at gcc dot gnu dot org [this message]
2007-11-26 17:58 ` fxcoudert at gcc dot gnu dot org
2007-11-26 18:16 ` michael dot a dot richmond at nasa dot gov
2007-11-26 23:11 ` burnus at gcc dot gnu dot org
2007-11-26 23:29 ` kargl at gcc dot gnu dot org
2007-11-27 13:09 ` michael dot a dot richmond at nasa dot gov
2007-11-27 15:00 ` kargl at gcc dot gnu dot org
2007-11-27 15:29 ` michael dot a dot richmond at nasa dot gov
2007-11-27 19:43 ` kargl at gcc dot gnu dot org
2007-11-27 20:28 ` kargl at gcc dot gnu dot org
2007-11-27 21:51 ` fxcoudert at gcc dot gnu dot org
2007-11-30 4:14 ` jvdelisle at gcc dot gnu dot org
2007-11-30 9:27 ` fxcoudert at gcc dot gnu dot 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=20071126174251.14875.qmail@sourceware.org \
--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).