public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: James Clarke <jrtc27@jrtc27.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][PR gdb/17046] Use standard setjmp.h on Darwin
Date: Mon, 15 Sep 2014 23:45:00 -0000	[thread overview]
Message-ID: <073395E1-3B91-4685-B663-77BD84C969EE@jrtc27.com> (raw)
In-Reply-To: <87iokova6d.fsf@redhat.com>

That’s where I got the fix from. Not quite sure why this include location
was chosen in the first place; `setjmp.h' was a standard header in pure
ANSI C. The only reason I can think of is that older versions had 
`setjmp.h’ which simply includes `machine/setjmp.h’, which had the actual
definitions.

James Clarke

> On 15 Sep 2014, at 22:35, Sergio Durigan Junior <sergiodj@redhat.com> wrote:
> 
> On Monday, September 15 2014, James Clarke wrote:
> 
>> 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.
> 
> Thanks.
> 
> I am not a Mac user, and I know nothing about the details of the system,
> but I did a little investigation and I think this is the right fix
> indeed.
> 
> FWIW, I found
> <https://lists.macosforge.org/pipermail/macports-tickets/2014-June/163911.html>
> which is a related discussion.
> 
> This is not an approval, BTW.
> 
> -- 
> Sergio
> GPG key ID: 0x65FC5E36
> Please send encrypted e-mail if possible
> http://sergiodj.net/

  reply	other threads:[~2014-09-15 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 21:25 James Clarke
2014-09-15 21:36 ` Sergio Durigan Junior
2014-09-15 23:45   ` James Clarke [this message]
2014-09-16  8:41 ` Tristan Gingold
2015-01-06 22:42   ` Simon Marchi
2015-01-12 13:41     ` Simon Marchi
2015-01-12 17:21       ` Joel Brobecker
2015-01-12 17:49         ` Simon Marchi

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=073395E1-3B91-4685-B663-77BD84C969EE@jrtc27.com \
    --to=jrtc27@jrtc27.com \
    --cc=gdb-patches@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: 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).