From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Weird directories after compiling emacs native mode and creating .deb package
Date: Sat, 01 May 2021 12:14:21 +0300 [thread overview]
Message-ID: <83a6peak9e.fsf@gnu.org> (raw)
In-Reply-To: <CAO48Bk8ctAsqKfTvVOyD7t=9qtGvisBm6p0s1oq_YU0kqmsKHQ@mail.gmail.com> (message from Pedro Andres Aranda Gutierrez on Sat, 1 May 2021 10:40:23 +0200)
> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> Date: Sat, 1 May 2021 10:40:23 +0200
> Cc: emacs-devel@gnu.org
>
> in an effort to answer you last email, I started cleaning up by debina/rules (aka Makefile) and have come up
> with a simpler setup that compiles and creates an installable emacs package (for the GUI version only) So it
> certainly was a problem of not setting sensible directories in the original Makefile.
>
> Currently, I'm stumbling with the next stone in my path. I can't get emacs to start:
>
> emacs ➤ emacs
> Symbol’s value as variable is void: auto-save-list-file-prefix
>
> If I start it in terminal mode, I get it to build the frames, but I get the same message on the mini-buffer and it
> doesn't load any file.
>
> Now compiling without native-comp gets me a perfectly working emacs in GUI and terminal mode
Sounds like something's wrong with your *.eln files, suggest to clean
up all the caches and start anew.
next prev parent reply other threads:[~2021-05-01 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 11:52 Weird directories after compiling emacs native mode and creating .deb package Pedro Andres Aranda Gutierrez
2021-04-30 14:00 ` Eli Zaretskii
2021-05-01 8:40 ` Pedro Andres Aranda Gutierrez
2021-05-01 9:14 ` Eli Zaretskii [this message]
2021-05-03 15:08 ` Pedro Andres Aranda Gutierrez
2021-05-01 9:02 ` Tatsuya Kinoshita
2021-05-01 9:16 ` Eli Zaretskii
2021-05-01 9:47 ` Tatsuya Kinoshita
2021-05-02 5:23 ` Pedro Andres Aranda Gutierrez
2021-05-02 6:36 ` Tatsuya Kinoshita
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=83a6peak9e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=paaguti@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 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).