bug#48446: closed (28.0.50; Native compile failure during bootstrap)

[GNU bug Tracking System]

Your message dated Sun, 16 May 2021 12:01:07 +0300
with message-id <83k0nzuk6k.fsf@gnu.org>
and subject line Re: bug#48446: 28.0.50; Native compile failure during bootstrap
has caused the debbugs.gnu.org bug report #48446,
regarding 28.0.50; Native compile failure during bootstrap
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
48446: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48446
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: 28.0.50; Native compile failure during bootstrap Date: Sat, 15 May 2021 12:40:39 -0400 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

I'm attempting to build the native compile using NATIVE_FULL_AOT=1 from
the master branch  from scratch.  I'm building from repository revision
46e4704e2abca4d264a43965f92eab7608211ee6.

During the final elisp compilation phase the process segfaults.

I've attached my config.log and the make output.  I'm using libgccjit
version 10.2.1-6 from Debian unstable.

config.log
Description: Text document

make.log
Description: Text document

-- 
Michael Welsh Duggan
(md5i@md5i.com)

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#48446: 28.0.50; Native compile failure during bootstrap
>
>
>
>
> Date: 
>
> Sun, 16 May 2021 12:01:07 +0300
>
>
>
>
> > From: Andrea Corallo <akrl@sdf.org>
> > Cc: mwd@md5i.com, acm@muc.de, 48446@debbugs.gnu.org
> > Date: Sun, 16 May 2021 08:00:42 +0000
> > 
> > > I think I know the answer: with natively-compiled Lisp, we can only
> > > call Lisp from init functions registered with
> > > pdumper_do_now_and_after_late_load, because the *.eln files are not
> > > loaded when functions registered with pdumper_do_now_and_after_load
> > > are run.  Andrea, is that conclusion correct?
> > 
> > AFAIR that is spot on, I've introduced the mechanism with 4fba79feee.
>
> Thanks, I'm therefore closing this bug report.
>
>
> --- End Message ---