public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <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: Tue, 08 Sep 2009 14:55:00 -0000 [thread overview] Message-ID: <20090908145516.32261.qmail@sourceware.org> (raw) In-Reply-To: <bug-41309-18169@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from kargl at gcc dot gnu dot org 2009-09-08 14:55 ------- (In reply to comment #1) > Created an attachment (id=18542) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18542&action=view) [edit] > file generated during build failure > > The same result arises during make when configure is run without further > options. The following SMC packages are installed on the system: > SMCgmp SMClgcc346 SMCliconv SMClintl SMCmake SMCmpfr SMCnetsnmp > SMCsed SMCsudo SMCtar SUNWmgts SUNWtsmc > followed by s source build and install of mpfr-2.4.1 > My first and only guess is that SMCmpfr and mpfr-2.4.1 are incompatible. For example, configure is finding the library for mpfr-2.4.1 but the build is finding the SMCmpfr header file. Try using the --with-mpfr configure option or remove one of the mpfr packages. PS: I note that you don't list a GMP package, but one must be present if you built mpfr-2.4.1. You may need/want to use the --with-gmp option. -- kargl at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|4.4.1 build of fortran fails|4.4.1 build of fortran fails |on T5140 |on T5140 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
next prev parent reply other threads:[~2009-09-08 14:55 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 [this message] 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=20090908145516.32261.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: 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).