From: Gergely Czuczy <gergely.czuczy@harmless.hu>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 28308@debbugs.gnu.org
Subject: bug#28308: Build failure on FreeBSD/aarch64
Date: Wed, 1 Nov 2017 19:27:10 +0100 [thread overview]
Message-ID: <6ef7dc53-d53f-5675-8f0b-376752cf075c@harmless.hu> (raw)
In-Reply-To: <CAM-tV-9GU3iQvtoZZKvzwH1xLRm-XDhYtcRU25PtU7Vc-Y7v0g@mail.gmail.com>
On 2017. 11. 01. 17:51, Noam Postavsky wrote:
> On Wed, Nov 1, 2017 at 12:14 PM, Gergely Czuczy
> <gergely.czuczy@harmless.hu> wrote:
>> On 2017. 10. 31. 18:31, Noam Postavsky wrote:
>>> diff --git a/configure.ac b/configure.ac
>>> index d294412dc4..2e690987a6 100644
>>> --- a/configure.ac
>>> +++ b/configure.ac
>> Is 2e690987a6 the commit id I can try? I would like to test it.
> No, that hash is for the configure.ac file only. To test the patch,
> save it to a file (e.g., call it bsd-hybridmalloc.diff) and then run
> 'git apply bsd-hybridmalloc.diff'.
>
> By the way, do you know about the status of Emacs on FreeBSD x86? It
> seems to me that the problem and solution are not specific to aarch64.
On x86 (as in 32 bit terms), I don't really know. All my systems are
amd64 ones, and on that one, it runs fine. However, I haven't checked
the development branch, just the release. That works fine.
But if that's any help, I can give it a shot tomorrow on amd64 as well,
and see how it goes.
Regarding the patch, I should apply it to the latest checkout, right?
next prev parent reply other threads:[~2017-11-01 18:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 16:34 bug#28308: Build failure on FreeBSD/aarch64 Gergely Czuczy
2017-08-31 16:47 ` Glenn Morris
2017-08-31 17:02 ` Gergely Czuczy
2017-09-02 3:13 ` npostavs
2017-09-04 12:32 ` Gergely Czuczy
2017-09-08 23:52 ` npostavs
2017-09-09 5:01 ` Gergely Czuczy
2017-09-09 7:07 ` Eli Zaretskii
2017-09-11 6:07 ` npostavs
2017-09-11 7:26 ` Gergely Czuczy
2017-09-11 14:45 ` Eli Zaretskii
2017-09-11 15:10 ` Gergely Czuczy
2017-09-11 15:31 ` Eli Zaretskii
2017-09-11 17:12 ` Gergely Czuczy
2017-09-11 17:17 ` Eli Zaretskii
2017-09-11 19:57 ` Gergely Czuczy
2017-09-11 20:33 ` Gergely Czuczy
2017-09-12 5:22 ` npostavs
2017-09-12 5:57 ` Gergely Czuczy
2017-09-12 14:59 ` Eli Zaretskii
2017-09-12 15:13 ` Gergely Czuczy
2017-09-20 5:51 ` Gergely Czuczy
2017-09-20 19:29 ` Noam Postavsky
2017-10-19 23:39 ` Noam Postavsky
2017-10-20 7:07 ` Eli Zaretskii
2017-10-24 18:43 ` Noam Postavsky
2017-10-31 17:31 ` Noam Postavsky
2017-10-31 20:21 ` Eli Zaretskii
2017-11-01 16:14 ` Gergely Czuczy
2017-11-01 16:51 ` Noam Postavsky
2017-11-01 18:27 ` Gergely Czuczy [this message]
2017-11-01 18:52 ` Noam Postavsky
2017-11-02 21:03 ` Gergely Czuczy
2017-11-04 23:14 ` Noam Postavsky
2017-11-05 18:10 ` Gergely Czuczy
2017-11-06 23:14 ` Noam Postavsky
2017-09-14 0:51 ` Paul Eggert
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=6ef7dc53-d53f-5675-8f0b-376752cf075c@harmless.hu \
--to=gergely.czuczy@harmless.hu \
--cc=28308@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).