unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gong-Yi Liao 廖宮毅" <gongyi.liao@gmail.com>
To: Frank Haun <fh@fhaun.de>
Cc: emacs-devel@gnu.org
Subject: Re: native-comp branch on Raspberry Pi 4
Date: Thu, 16 Apr 2020 12:06:48 -0500	[thread overview]
Message-ID: <CALKwrMAAkaiM3765f3LzEUyxsZeKuYeHn8Lemm9N+athRXm1tQ@mail.gmail.com> (raw)
In-Reply-To: <87pnc7e6zt.fsf@u12000.fhaun.de>

[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]

I got exactly the same error with gcc 8/9/10  on a raspberry pi 4 running
Debian buster/Sid and fedora 31/rawhide in podman container.

It seems in gccjit issue as the hello world example on gccjit doc web site
does not compile on raspberry pi 4 as  well

On Thu, Apr 16, 2020, 11:23 Frank Haun <fh@fhaun.de> wrote:

> Hello,
>
> I'm not sure, should this branch compile on ARM Devices?
>
> I've tried Raspbian 32bit and Ubuntu Core 64bit.
>
> All necessary libs are installed.
>
> | $ git status
> | On branch feature/native-comp
> | Your branch is up to date with 'origin/feature/native-comp'.
>
> | $ ./autogen.sh
> | $ ./configure --without-imagemagick --with-x-toolkit=lucid --with-pop
> --with-jpeg=no --with-gif=no --with-tiff=no --without-makeinfo
> | $ make
>
> First everything does fine, but then I get this:
>
> | ...
> | Loading /home/ubuntu/CVS/emacs/lisp/tooltip.el (source)...
> | Finding pointers to doc strings...
> | Finding pointers to doc strings...done
> | Dumping under the name bootstrap-emacs.pdmp
> | dumping fingerprint:
> 9be4874d483d5c67b257e1d30440bebceb4673d531a3b39f69150175f6101e76
> | Dump complete
> | Byte counts: header=96 hot=14987776 discardable=122208 cold=9776976
> | Reloc counts: hot=1010305 discardable=6007
> | make -C ../lisp compile-first EMACS="../src/bootstrap-emacs"
> | make[2]: Entering directory '/home/ubuntu/CVS/emacs/lisp'
> |   ELC      emacs-lisp/macroexp.elc
> | /bin/bash: line 1: 24525 Segmentation fault      (core dumped)
> EMACSLOADPATH= '../src/bootstrap-emacs' -batch --no-site-file
> --no-site-lisp --eval '(setq load-prefer-newer t)' -f batch-byte-compile
> emacs-lisp/macroexp.el
> | make[2]: *** [Makefile:316: emacs-lisp/macroexp.elc] Error 139
> | make[2]: Leaving directory '/home/ubuntu/CVS/emacs/lisp'
> | make[1]: *** [Makefile:828: bootstrap-emacs.pdmp] Error 2
> | make[1]: Leaving directory '/home/ubuntu/CVS/emacs/src'
> | make: *** [Makefile:424: src] Error 2
>
> Frank
> --
> Linux ubuntu 5.3.0-1022 aarch64 GNU/Linux
> Experimental Blog: <http://fhaun.de>
>
>
>

[-- Attachment #2: Type: text/html, Size: 2630 bytes --]

  reply	other threads:[~2020-04-16 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 16:17 native-comp branch on Raspberry Pi 4 Frank Haun
2020-04-16 17:06 ` Gong-Yi Liao 廖宮毅 [this message]
2020-04-16 17:18   ` Andrea Corallo
2020-04-16 18:50     ` Gong-Yi Liao 廖宮毅
2020-04-16 19:35       ` Andrea Corallo

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=CALKwrMAAkaiM3765f3LzEUyxsZeKuYeHn8Lemm9N+athRXm1tQ@mail.gmail.com \
    --to=gongyi.liao@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=fh@fhaun.de \
    /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).