public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/19481] libgfortran doesn't build -- configure doesn't handle cabs() well
Date: Sun, 01 May 2005 14:33:00 -0000	[thread overview]
Message-ID: <20050501143318.2393.qmail@sourceware.org> (raw)
In-Reply-To: <20050117132420.19481.coudert@clipper.ens.fr>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-01 14:33 -------
(In reply to comment #2)
> I worked around this bug, commenting a line in /mingw/include/math.h (I quote it
> here for reference):
> //_CRTIMP double __cdecl cabs (struct _complex);
> 
> The end of the compilation runs smoothly, but when I try to use gfortran, it
> complains at link-time about missing symbol _ftruncate. Indeed, mingw doesn't
> have a ftruncate (it has a chsize which has the same prototype and all), but the

The ftruncate problem should be fixed now.

Does this work fully or is cabs issue still there?

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19481


  parent reply	other threads:[~2005-05-01 14:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-17 13:24 [Bug bootstrap/19481] New: " coudert at clipper dot ens dot fr
2005-01-17 15:15 ` [Bug libfortran/19481] " pinskia at gcc dot gnu dot org
2005-01-17 15:55 ` pinskia at gcc dot gnu dot org
2005-01-17 17:10 ` coudert at clipper dot ens dot fr
2005-05-01 14:33 ` pinskia at gcc dot gnu dot org [this message]
2005-05-02  7:42 ` fxcoudert at gcc dot gnu dot org
2005-05-31 17:06 ` giovannibajo at libero dot it
2005-09-05 10:37 ` fxcoudert at gcc dot gnu dot org
2005-09-07 14:10 ` pinskia 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=20050501143318.2393.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).