public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/38268] gfortran doesn't link any 64 bits binaries on Solaris Date: Wed, 26 Nov 2008 07:50:00 -0000 [thread overview] Message-ID: <20081126074856.8269.qmail@sourceware.org> (raw) In-Reply-To: <bug-38268-12750@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from ebotcazou at gcc dot gnu dot org 2008-11-26 07:48 ------- > I have been given access to a mchine with this architecture and have not, > after several evenings at it, been able to complete a single build of > gfortran. Weird, folks generally can build it flawlessly, see the various build pages: http://gcc.gnu.org/gcc-4.1/buildstat.html http://gcc.gnu.org/gcc-4.2/buildstat.html http://gcc.gnu.org/gcc-4.3/buildstat.html You indeed need to follow the build instructions. What happens exactly? > I suspect there are some configuration issues going on here that we need to > nail down. Do we have a "solaris" gcc maintainer around? I'm the SPARC/Solaris maintainer. The Fortran compiler has been working fine on this platform since 4.0.0, like on every other primary platforms. -- ebotcazou at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ebotcazou at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38268
next prev parent reply other threads:[~2008-11-26 7:50 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-25 21:47 [Bug fortran/38268] New: " mt1 at systella dot fr 2008-11-26 3:54 ` [Bug fortran/38268] " jvdelisle at gcc dot gnu dot org 2008-11-26 7:19 ` mt1 at systella dot fr 2008-11-26 7:50 ` ebotcazou at gcc dot gnu dot org [this message] 2008-11-26 8:07 ` ebotcazou at gcc dot gnu dot org 2008-11-26 8:28 ` mt1 at systella dot fr 2008-11-26 11:41 ` ebotcazou at gcc dot gnu dot org 2008-12-03 4:08 ` jvdelisle at gcc dot gnu dot org 2008-12-03 9:14 ` ebotcazou at gcc dot gnu dot org 2008-12-05 5:47 ` jvdelisle at gcc dot gnu dot org 2008-12-05 7:41 ` ebotcazou 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=20081126074856.8269.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).