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] New: 4.4.1 build of fortran fails on T5140 Date: Tue, 08 Sep 2009 14:32:00 -0000 [thread overview] Message-ID: <bug-41309-18169@http.gcc.gnu.org/bugzilla/> (raw) after successful build & install 4.4.1 c,c++, attempt to build all languages fails with: configure: error: GNU Fortran is not working; please report a bug in http://gcc.gnu.org/bugzilla my config script is: PATH=/usr/local/bin:$PATH export PATH CC="" CFLAGS="" unset CC unset CFLAGS ../gcc-4.4.1/configure \ --without-gnu-ld \ --with-ld=/usr/ccs/bin/ld \ --enable-shared my make script is: PATH=/usr/local/bin:$PATH CC="" CFLAGS="" unset CC unset CFLAGS export PATH CC make -j 40 $@ I will submit this and then see how to attach the detailed report ./build/sparc-sun-solaris2.10/libgfortran/config.log -- Summary: 4.4.1 build of fortran fails on T5140 Product: gcc Version: 4.4.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ian dot james at bnymellon dot com GCC build triplet: sparc-sun-solaris2.10 GCC host triplet: sparc-sun-solaris2.10 GCC target triplet: sparc-sun-solaris2.10 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
next reply other threads:[~2009-09-08 14:32 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-08 14:32 ian dot james at bnymellon dot com [this message] 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 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=bug-41309-18169@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).