unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 24892@debbugs.gnu.org
Subject: bug#24892: {s, }brk removed from FreeBSD 11.x and later, arm64 architecture
Date: Sat, 19 Nov 2016 09:20:50 +0200	[thread overview]
Message-ID: <83r368aqb1.fsf@gnu.org> (raw)
In-Reply-To: <1dc6fa8c-7378-6e4e-1d9e-86c962fc48bb@cs.ucla.edu> (message from Paul Eggert on Fri, 18 Nov 2016 14:22:07 -0800)

unblock 21966 by 24892
block 24655 by 24892
thanks

> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 18 Nov 2016 14:22:07 -0800
> Cc: freebsd-hackers@freebsd.org, Brooks Davis <brooks@freebsd.org>,
> 	24892@debbugs.gnu.org, Ashish SHUKLA <ashish.is@lostca.se>
> 
> Ed Maste wrote:
> > arm64 support was first available in a release in FreeBSD 11.0, without sbrk, and sbrk never existed on the stable/11 branch.
> 
> Thanks, I didn't know that. So Emacs has never worked in this environment.

Since Emacs never worked on FreeBSD/arm64, we don't need to block the
release of 25.2 on this issue (although it would be nice to have it
resolved by 25.2).





  parent reply	other threads:[~2016-11-19  7:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07  6:01 bug#24892: {s, }brk removed from FreeBSD 11.x and later, arm64 architecture Ashish SHUKLA
2016-11-07 15:19 ` Eli Zaretskii
2016-11-08 17:54 ` Paul Eggert
2016-11-08 20:11   ` Eli Zaretskii
2016-11-08 21:41     ` Paul Eggert
2016-11-09  3:34       ` Eli Zaretskii
2016-11-09  8:27         ` Paul Eggert
2016-11-09 15:49           ` Eli Zaretskii
2016-11-10  1:47             ` Paul Eggert
2016-11-10 16:13               ` Eli Zaretskii
2016-11-10 16:59                 ` Paul Eggert
2016-11-10 17:24                   ` Eli Zaretskii
2016-11-10  0:22       ` Richard Stallman
2016-11-10  1:40         ` Paul Eggert
2016-11-09  4:29 ` Ashish SHUKLA
2016-11-09  8:26   ` Paul Eggert
2016-11-09  9:46     ` Andreas Schwab
2016-11-09 15:50       ` Eli Zaretskii
2016-11-09 17:52       ` Paul Eggert
2016-11-10  9:52         ` Andreas Schwab
2016-11-10 16:23           ` Paul Eggert
2016-11-10 17:00             ` Andreas Schwab
2016-11-10 17:22               ` Paul Eggert
2016-11-10 17:33                 ` Andreas Schwab
2016-11-11  2:48                   ` Paul Eggert
2016-11-17 17:27                     ` Eli Zaretskii
2016-11-18 12:29                       ` Ashish SHUKLA
2016-11-18 16:21                         ` Paul Eggert
2016-11-18 20:20                           ` Ed Maste
2016-11-18 20:23                           ` Brooks Davis
     [not found]                           ` <CAPyFy2AL_OZWYpp+tiLSro_3WK1-H8Pdjy4-ZhUQChMQqageUw@mail.gmail.com>
2016-11-18 22:22                             ` Paul Eggert
2016-11-19  6:57                               ` Eli Zaretskii
2016-11-19  7:20                               ` Eli Zaretskii [this message]
2017-09-02 13:37                                 ` Eli Zaretskii
2016-11-09 13:23     ` Ashish SHUKLA

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r368aqb1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24892@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).