public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61407] Build errors on latest OS X 10.10 Yosemite with Xcode 6 on GCC 4.8.3
Date: Sat, 15 Nov 2014 15:52:00 -0000	[thread overview]
Message-ID: <bug-61407-4-jcgSCfIja0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61407-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61407

--- Comment #55 from howarth at bromo dot med.uc.edu ---
(In reply to Derrick Kay from comment #53)

If you just want the gfortran compiler for Yosemite, either install the gcc49
package under the fink (http://www.finkproject.org), MacPorts
(http://www.macports.org) or homebrew (http://brew.sh) packaging systems. Also,
a stand-alone installation of gfortran for Yosemite is available at
http://hpc.sourceforge.net.


  parent reply	other threads:[~2014-11-15 15:52 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  5:41 [Bug target/61407] New: " kassafari at gmail dot com
2014-06-04  5:54 ` [Bug target/61407] " pinskia at gcc dot gnu.org
2014-06-04  6:05 ` pinskia at gcc dot gnu.org
2014-06-04  7:21 ` kassafari at gmail dot com
2014-06-04  8:52 ` schwab@linux-m68k.org
2014-06-06 19:03 ` pinskia at gcc dot gnu.org
2014-06-06 19:06 ` pinskia at gcc dot gnu.org
2014-06-17  9:09 ` morpheby at gmail dot com
2014-06-17  9:48 ` manu at gcc dot gnu.org
2014-06-17 10:02 ` morpheby at gmail dot com
2014-06-20 12:27 ` egall at gwmail dot gwu.edu
2014-06-28  4:20 ` ericmark26 at gmail dot com
2014-07-20 16:24 ` dominyktiller at gmail dot com
2014-07-21 21:41 ` jrtc27 at jrtc27 dot com
2014-07-21 21:43 ` jrtc27 at jrtc27 dot com
2014-07-24 13:34 ` jrtc27 at jrtc27 dot com
2014-07-24 15:27 ` alexandermbock at gmail dot com
2014-07-31  2:12 ` alexandermbock at gmail dot com
2014-07-31 10:09 ` jrtc27 at jrtc27 dot com
2014-07-31 12:34 ` aggrostyle at gmail dot com
2014-08-02 16:12 ` ericmark26 at gmail dot com
2014-08-22 16:06 ` dominyktiller at gmail dot com
2014-08-25 18:17 ` jrtc27 at jrtc27 dot com
2014-08-26 16:05 ` jrtc27 at jrtc27 dot com
2014-08-26 17:28 ` howarth.at.gcc at gmail dot com
2014-08-26 18:18 ` jrtc27 at jrtc27 dot com
2014-08-26 19:39 ` howarth.at.gcc at gmail dot com
2014-08-26 20:41 ` morpheby at gmail dot com
2014-08-27 18:02 ` jrtc27 at jrtc27 dot com
2014-09-08 21:41 ` larryv at macports dot org
2014-09-09  5:08 ` larryv at macports dot org
2014-09-09 20:59 ` larryv at macports dot org
2014-09-10  0:36 ` larryv at macports dot org
2014-09-14  8:06 ` fxcoudert at gcc dot gnu.org
2014-09-29 18:41 ` fxcoudert at gcc dot gnu.org
2014-10-27 19:19 ` jeremyhu at macports dot org
2014-10-27 19:37 ` jeremyhu at macports dot org
2014-11-10 16:34 ` fxcoudert at gcc dot gnu.org
2014-11-10 20:27 ` fxcoudert at gcc dot gnu.org
2014-11-10 20:29 ` fxcoudert at gcc dot gnu.org
2014-11-11  2:01 ` jeremyhu at macports dot org
2014-11-11  8:18 ` fxcoudert at gcc dot gnu.org
2014-11-14  9:39 ` larryv at macports dot org
2014-11-15 14:26 ` derrick.k at gmx dot de
2014-11-15 14:54 ` fxcoudert at gcc dot gnu.org
2014-11-15 15:52 ` howarth at bromo dot med.uc.edu [this message]
2014-12-18 20:13 ` fxcoudert at gcc dot gnu.org
2021-08-07  1:15 ` pinskia at gcc dot gnu.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-61407-4-jcgSCfIja0@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: 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).