public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/24991] [4.1/4.2 Regression] gfortran build fails with - error:gthr-default.h: No such file or directory
Date: Tue, 13 Dec 2005 08:31:00 -0000 [thread overview]
Message-ID: <20051213083148.25936.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24991-10129@http.gcc.gnu.org/bugzilla/>
------- Comment #43 from jakub at gcc dot gnu dot org 2005-12-13 08:31 -------
Subject: Bug 24991
Author: jakub
Date: Tue Dec 13 08:31:41 2005
New Revision: 108471
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108471
Log:
PR libfortran/24991
* acinclude.m4 (LIBGFOR_CHECK_PRAGMA_WEAK): Rename to...
(LIBGFOR_GTHREAD_WEAK): ... this. Define SUPPORTS_WEAK rather
than HAVE_PRAGMA_WEAK. Define GTHREAD_USE_WEAK to 0 on hosts
that shouldn't use weak in gthr.h.
* configure.ac: Use LIBGFOR_GTHREAD_WEAK instead of
LIBGFOR_CHECK_PRAGMA_WEAK.
* config.h.in: Regenerated.
* configure: Regenerated.
* io/io.h (SUPPORTS_WEAK): Don't define here.
* intrinsics/ftell.c (ftell, FTELL_SUB): Add unlock_unit call.
* intrinsics/fget.c (fgetc, fputs): Likewise.
* intrinsics/tty.c (ttynam): Likewise.
Modified:
trunk/libgfortran/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991
next prev parent reply other threads:[~2005-12-13 8:31 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 21:43 [Bug libfortran/24991] New: " dir at lanl dot gov
2005-11-22 21:58 ` [Bug libfortran/24991] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2005-11-23 9:10 ` jakub at gcc dot gnu dot org
2005-11-23 14:09 ` dir at lanl dot gov
2005-11-23 15:45 ` jakub at gcc dot gnu dot org
2005-11-23 16:05 ` bonzini at gcc dot gnu dot org
2005-11-23 17:47 ` dir at lanl dot gov
2005-11-23 17:53 ` pinskia at gcc dot gnu dot org
2005-11-23 19:46 ` dir at lanl dot gov
2005-11-23 20:24 ` jakub at gcc dot gnu dot org
2005-11-23 21:18 ` dir at lanl dot gov
2005-11-23 21:57 ` jakub at gcc dot gnu dot org
2005-11-23 22:09 ` dir at lanl dot gov
2005-11-23 22:12 ` jakub at gcc dot gnu dot org
2005-11-23 22:34 ` bonzini at gcc dot gnu dot org
2005-11-24 8:36 ` jakub at gcc dot gnu dot org
2005-11-24 13:38 ` jb at gcc dot gnu dot org
2005-11-25 11:32 ` jakub at gcc dot gnu dot org
2005-11-25 11:32 ` jakub at gcc dot gnu dot org
2005-11-25 11:42 ` jakub at gcc dot gnu dot org
2005-11-25 16:51 ` howarth at nitro dot med dot uc dot edu
2005-11-25 17:05 ` jakub at gcc dot gnu dot org
2005-11-25 17:36 ` howarth at nitro dot med dot uc dot edu
2005-11-25 19:22 ` howarth at nitro dot med dot uc dot edu
2005-11-25 20:52 ` pinskia at gcc dot gnu dot org
2005-11-25 20:53 ` pinskia at gcc dot gnu dot org
2005-11-25 20:54 ` pinskia at gcc dot gnu dot org
2005-11-25 21:01 ` pinskia at gcc dot gnu dot org
2005-11-25 21:27 ` pinskia at gcc dot gnu dot org
2005-11-25 21:54 ` howarth at nitro dot med dot uc dot edu
2005-11-25 22:06 ` geoffk at gcc dot gnu dot org
2005-11-25 22:43 ` andreast at gcc dot gnu dot org
2005-11-25 22:52 ` jakub at gcc dot gnu dot org
2005-11-25 23:03 ` howarth at nitro dot med dot uc dot edu
2005-11-26 2:27 ` howarth at nitro dot med dot uc dot edu
2005-11-26 2:50 ` howarth at nitro dot med dot uc dot edu
2005-11-28 14:16 ` aoliva at gcc dot gnu dot org
2005-11-28 15:53 ` dir at lanl dot gov
2005-11-29 0:47 ` aoliva at gcc dot gnu dot org
2005-11-29 0:56 ` aoliva at gcc dot gnu dot org
2005-12-09 9:03 ` fxcoudert at gcc dot gnu dot org
2005-12-09 9:12 ` jakub at gcc dot gnu dot org
2005-12-09 13:50 ` jakub at gcc dot gnu dot org
2005-12-13 8:19 ` jakub at gcc dot gnu dot org
2005-12-13 8:31 ` jakub at gcc dot gnu dot org [this message]
2005-12-14 13:37 ` jakub 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=20051213083148.25936.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).