public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "derrick.k at gmx dot de" <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 14:26:00 -0000	[thread overview]
Message-ID: <bug-61407-4-h1eyR1LNPH@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

Derrick Kay <derrick.k at gmx dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |derrick.k at gmx dot de

--- Comment #53 from Derrick Kay <derrick.k at gmx dot de> ---
Hi guys,

sorry for asking such a stupid question here: I wanted to install and use
Fortran on my Mac (never used it before) and ran into the problems with
compiling described here.

I have basically two questions:

1) which one of the patches reported and listed above shall I use?
2) I tried all of them, but I seem to have difficulties implementing them.
Someone suggested to go to the appropriate directory where gcc is stored (i.e.
SSD1 ▸ Applications ▸ Xcode ▸ Contents ▸ Developer ▸ usr ▸ bin) store the patch
file there (as a .diff, right?) and then execute in the terminal

patch -p1 < patchfilename.diff

then, i get

wlan251-121:patch3 Derrick$ patch -p1 < patch.diff
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
b/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
|index 196eb3b..d55e200 100644
|--- a/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
|+++ b/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
--------------------------
File to patch: 

i enter gcc, and then i get

patching file gcc
Hunk #1 FAILED at 835.
1 out of 1 hunk FAILED -- saving rejects to file gcc.rej
can't find file to patch at input line 18
Perhaps you used the wrong -p or --strip option?

I am really new to all of this... any hint on how to implement one of the
patches, and ideally which patch to use, would be very much appreciated. thank
you, best,
derrick
>From gcc-bugs-return-466859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 15 14:29:08 2014
Return-Path: <gcc-bugs-return-466859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28852 invoked by alias); 15 Nov 2014 14:29:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28823 invoked by uid 48); 15 Nov 2014 14:29:04 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63886] float will fit into int with abs - possible missing warning Wabsolute-value
Date: Sat, 15 Nov 2014 14:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63886-4-u38KLJDnDA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63886-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63886-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg01331.txt.bz2
Content-length: 132

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc886

--- Comment #4 from Andreas Schwab <schwab@linux-m68k.org> ---
float f = 3.1f;


  parent reply	other threads:[~2014-11-15 14:26 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 [this message]
2014-11-15 14:54 ` fxcoudert at gcc dot gnu.org
2014-11-15 15:52 ` howarth at bromo dot med.uc.edu
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-h1eyR1LNPH@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).