bug#62655: closed (30.0.50; Build error (in case of NATIVECOMP?): “org-plot.el" "block does not end with a branch"”)

[GNU bug Tracking System]

Your message dated Sun, 1 Oct 2023 02:36:02 -0700
with message-id 
<CADwFkmk=z9fA7Jn-CW9asUBU4mYYyp5PaA0dwHNzuatpUhDNfQ@mail.gmail.com>
and subject line Re: bug#62596: make bootstrap failing since 52b67740d10
has caused the debbugs.gnu.org bug report #62596,
regarding 30.0.50; Build error (in case of NATIVECOMP?): “org-plot.el" "block 
does not end with a branch"”
to be marked as done.

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


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

--- Begin Message --- Subject: 30.0.50; Build error (in case of NATIVECOMP?): “org-plot.el" "block does not end with a branch"” Date: Mon, 03 Apr 2023 20:29:29 +0000 GNU Emacs, master branch, latest commits, e.g. 0275c54ca80124f8a6e3a9823844b9ee131443cc, fails to build. The full build error for attempting to install Emacs with Guix ("guix install emacs-next-tree-sitter --with-branch=emacs-next-tree-sitter=master") is attached.

FreeBSD also has this issue. They seem to work it around by disabling NATIVECOMP. So, it seems to related to native compilation. https://cgit.freebsd.org/ports/commit/?id=73560fbfd1950eec2da204856d5698905e299273

Garuda Linux also seems to have this issue. https://builds.garudalinux.org/repos/chaotic-aur/logs/emacs-pgtk-native-comp-git.log

log.txt
Description: Text document

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#62596: make bootstrap failing since 52b67740d10
>
>
>
>
> Date: 
>
> Sun, 1 Oct 2023 02:36:02 -0700
>
>
>
>
> Adam Sjøgren via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs@gnu.org> writes:
>
> > Stefan writes:
> >
> >> This bug is still open.  Is this still an issue, or has it been
> >> resolved since?
> >
> > 'make bootstrap' works for me with (master updated yesterday), so from
> > my (superficial) perspective it has been fixed.
> >
> > Thanks for checking in!
>
> Thanks, I'm therefore closing this bug report.
>
>
> --- End Message ---