public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dir at lanl dot gov" <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: Wed, 23 Nov 2005 19:46:00 -0000 [thread overview]
Message-ID: <20051123194559.28461.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24991-10129@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from dir at lanl dot gov 2005-11-23 19:45 -------
I did a complete rebuild with the same results -
mkdir gfortran
cd gfortran
svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc
cd gcc
patch -p0 < /Users/dir/Desktop/gcc41-pr24991.patch
configure --prefix=/Users/dir/gfortran --enable-languages=c,f95
make -j 4
make install
[dranta:~/sage/ibar/ibarOne] dir% rage20051111GF.x ibarOne.input
dyld: lazy symbol binding failed: Symbol not found: ___gthrw_pthread_mutex_lock
Referenced from: /Users/dir/gfortran/lib/libgfortran.1.dylib
Expected in: flat namespace
dyld: Symbol not found: ___gthrw_pthread_mutex_lock
Referenced from: /Users/dir/gfortran/lib/libgfortran.1.dylib
Expected in: flat namespace
Trace/BPT trap
I built a new version last week and it works fine -
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.3.0
Configured with: ./configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.1.0 20051114 (experimental)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991
next prev parent reply other threads:[~2005-11-23 19:46 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 [this message]
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
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=20051123194559.28461.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).