public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/17046] Will not build on OS X 10.10 Yosemite. Date: Mon, 12 Jan 2015 17:19:00 -0000 [thread overview] Message-ID: <bug-17046-4717-lDVBRGzxjE@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17046-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17046 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Joel Brobecker <brobecke@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4ac15b59f2f506ff0ad59f148275cd7406b8d765 commit 4ac15b59f2f506ff0ad59f148275cd7406b8d765 Author: James Clarke <jrtc27@jrtc27.com> Date: Mon Jan 12 21:13:54 2015 +0400 [darwin/gdb] Use <setjmp.h> instead of <machine/setjmp.h> The `machine/setjmp.h' header is no longer present on OS X 10.10, and is non-standard. Instead, `darwin-nat.c' should be using the standard `setjmp.h' header. gdb/ChangeLog: 2015-01-12 James Clarke <jrtc27@jrtc27.com> (tiny patch) PR gdb/17046 * darwin-nat.c: Replace <machine/setjmp.h> #include by <setjmp.h> #include. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-01-12 17:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-10 14:58 [Bug gdb/17046] New: Will not build on Yosemite adaminsull at me dot com 2014-06-10 15:00 ` [Bug gdb/17046] " adaminsull at me dot com 2014-08-04 21:49 ` [Bug gdb/17046] Will not build on OS X 10.10 Yosemite rickard.von.essen at gmail dot com 2014-09-15 21:34 ` jrtc27 at jrtc27 dot com 2015-01-12 17:19 ` cvs-commit at gcc dot gnu.org [this message] 2015-01-12 17:22 ` brobecker at gnat dot com
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-17046-4717-lDVBRGzxjE@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).