public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian dot james at bnymellon dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41309] 4.4.1 build of fortran fails on T5140
Date: Mon, 21 Sep 2009 08:00:00 -0000 [thread overview]
Message-ID: <20090921075947.9811.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41309-18169@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from ian dot james at bnymellon dot com 2009-09-21 07:59 -------
I separated the directories of Solaris packaged GNU (/usr/sfw), open built GNU
(/usr/local) and locally built GNU components (usr/gnu) components, putting the
built ones earlier in LD_LIBRARY_PATH and PATH. I then rebuilt from source
using gcc-3.4.6 the packages mpfr, gmp. Then rebuilt gcc-4.4.1 and it has
worked. Then rebuilt mpfr and gmp using gcc-4.4.1 which has all worked.
Please mark the bug as user error.
Sorry for the false alert.
--
ian dot james at bnymellon dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian dot james at bnymellon
| |dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
next prev parent reply other threads:[~2009-09-21 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 14:32 [Bug fortran/41309] New: " ian dot james at bnymellon dot com
2009-09-08 14:39 ` [Bug fortran/41309] " ian dot james at bnymellon dot com
2009-09-08 14:55 ` kargl at gcc dot gnu dot org
2009-09-08 14:56 ` kargl at gcc dot gnu dot org
2009-09-08 17:34 ` mikael at gcc dot gnu dot org
2009-09-20 21:08 ` pinskia at gcc dot gnu dot org
2009-09-21 8:00 ` ian dot james at bnymellon dot com [this message]
2009-09-21 10:04 ` burnus 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=20090921075947.9811.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).