all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: "andres.ramirez" <rrandresf@gmail.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs 23.4 arm64 build
Date: Sun, 17 May 2020 21:43:21 +0200	[thread overview]
Message-ID: <CAGK7Mr48duuvUNb_87Px9Anc5j37Xy65xKOPnOyPNFam0hxe5A@mail.gmail.com> (raw)
In-Reply-To: <86tv0equml.fsf@gmail.com>

> uname -a
> Linux sacsa 5.6.7-1-ARCH #1 SMP PREEMPT Fri Apr 24 16:11:00 UTC 2020 armv7l GNU/Linux
> ~ $ pacman -Qi emacs23

Ah good idea, I'll look what gentoo does.

>     Philippe> It looks like 23.4 does not build on i386 but this I
>     Philippe> should be able to sort it out.
>
> I have compiled on i686 a month ago with the gentoo patches without
> issue. But perhaps your issue could be 'nokaslr' (kernel aslr)

I have found out that `uname -m` in i386 containers returns x86_64. If
I do `linux32 ./configure (..flags..)` then everything builds alright
for i386.

> Also my emacs23 compilation or arm (32 bits) was with 'CANNOT_DUMP=yes'
> and It is without any x-toolkit. for CI this is not going to work. You
> need a clean compilation same as in i686.

Yeah you just need to disable ASLR when building, and for old images
without X toolkit is ok. People are already happy with the amd64
image, I'm just trying to build the same dockerfile to arm64
(https://github.com/Silex/docker-emacs/blob/master/23.4/ubuntu/14.04/bootstrap/dev/Dockerfile).

I'll try your suggestions and report.

Thanks,
Philippe



      reply	other threads:[~2020-05-17 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 11:32 Emacs 23.4 arm64 build Philippe Vaucher
2020-05-17 17:00 ` Paul Eggert
2020-05-17 17:17   ` Philippe Vaucher
2020-05-17 18:33     ` andres.ramirez
2020-05-17 19:43       ` Philippe Vaucher [this message]

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=CAGK7Mr48duuvUNb_87Px9Anc5j37Xy65xKOPnOyPNFam0hxe5A@mail.gmail.com \
    --to=philippe.vaucher@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rrandresf@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.