From: Lin Sun <sunlin7.mail@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73855@debbugs.gnu.org
Subject: bug#73855: [BUG] Error: void-function (rx) during generating autoloads for python.el when building from source
Date: Wed, 13 Nov 2024 17:13:14 +0000 [thread overview]
Message-ID: <CABCREdrSRjHRY-aEunRBpOBiDTBr5j2vmbV20Q5o=V+o-2BdVg@mail.gmail.com> (raw)
In-Reply-To: <86zfm3kx0p.fsf@gnu.org>
On Wed, Nov 13, 2024 at 2:51 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Lin Sun <sunlin7.mail@gmail.com>
> > Date: Wed, 13 Nov 2024 00:31:07 +0000
> > I met a compile issue while generating the autoloads.el from
> > python.el, it seems the `python--auto-mode-alist-regexp` is defined
> > with 'rx' but the 'rx' wasn't loaded.
> > Should relate to the commit `2f485e68ff96cc66a17df2c0a58e272bbfc24765`
> > Add Python "*.pth" files to auto-mode-alist
> > * lisp/progmodes/python.el (python--auto-mode-alist-regexp): New
> > variable.
> >
> > Here is the errors:
>
> Thanks, but what is the recipe for reproducing this? just "make
> bootstrap" or something else?
>
> And in what branch? Your bug report lacks any information about your
> OS, Emacs configuration and version, and the build details.
Hi Eli,
Thanks for replying, the error happened when I compiled the master
branch (a7400cb8810) on Ubuntu 20.04, clang-20, libgccjit-14.
I spent more than 1 hours to search what caused the issue on my local
but didn't find the root cause, clean up and rebuild didn't help, so I
posted the error messages to mail list for searching helping.
This morning I checked out the latest master branch and started a
fresh building and everything works perfectly.
The issue should be my local issue (maybe related to some environment
variables or dependent libraries). I'm still keeping my eyes on it,
and will investigate the root cause if it happens again.
Please close this ticket, thanks, appreciate it!
next prev parent reply other threads:[~2024-11-13 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 23:24 bug#73855: [PATCH] * lisp/autorevert.el: Avoid reverting buffer in short time Lin Sun
2024-10-18 7:50 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-19 5:58 ` Lin Sun
2024-10-19 9:06 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-19 17:52 ` Lin Sun
2024-10-20 9:15 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-20 18:29 ` Lin Sun
2024-11-13 0:31 ` bug#73855: [BUG] Error: void-function (rx) during generating autoloads for python.el when building from source Lin Sun
2024-11-13 14:51 ` Eli Zaretskii
2024-11-13 17:13 ` Lin Sun [this message]
2024-11-14 7:39 ` Eli Zaretskii
2024-11-14 9:35 ` Andreas Röhler
2024-11-17 14:08 ` Stefan Kangas
2024-11-17 16:04 ` Lin Sun
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='CABCREdrSRjHRY-aEunRBpOBiDTBr5j2vmbV20Q5o=V+o-2BdVg@mail.gmail.com' \
--to=sunlin7.mail@gmail.com \
--cc=73855@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).