From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Compiling Emacs from source for hacking on it
Date: Tue, 31 May 2022 15:35:56 +0200 [thread overview]
Message-ID: <YpYZvCfOhIhOVxiE@tuxteam.de> (raw)
In-Reply-To: <874k15an1p.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Tue, May 31, 2022 at 08:45:06PM +0800, Po Lu wrote:
> Akib Azmain Turja <akib@disroot.org> writes:
>
> > I have recently (shallow) cloned Emacs source code. I have compiled it
> > by doing the following:
> >
> > $ mkdir build
> > $ cd build
> > $ ../configure --without-x --without-gnutls --without-modules \
> > --without-sqlite3 --without-pop --without-mailutils --without-sound
> > $ make
> >
> > If I understand correctly, running ./src/emacs should start the newly
> > compiled Emacs. But it says that with-memoizaton function definition is
> > void, even with an empty init file (actually I commented out the whole
> > file). ./src/temacs works, but says function-documention is undefined
> > at runtime.
> >
> > Am I doing something wrong?
>
> I think out of tree builds never really worked in Emacs.
Hm. FWIW I build regularly out-of-tree. I make sure to radically
delete the build dir, and do a "make distclean" (possibly not
needed).
The only issues I had were, from time to time, older .elc files
(thus that "double cleaning" above: that's how voodoo rituals
grow ;-)
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-05-31 13:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 12:07 Compiling Emacs from source for hacking on it Akib Azmain Turja
2022-05-31 12:45 ` Po Lu
2022-05-31 13:35 ` tomas [this message]
2022-05-31 13:42 ` Ken Brown
2022-05-31 14:01 ` tomas
2022-05-31 14:02 ` Óscar Fuentes
2022-05-31 14:10 ` tomas
2022-05-31 14:18 ` Óscar Fuentes
2022-05-31 16:27 ` Akib Azmain Turja
2022-05-31 16:55 ` Lars Ingebrigtsen
2022-05-31 18:16 ` Akib Azmain Turja
2022-05-31 18:18 ` Lars Ingebrigtsen
2022-05-31 13:06 ` Eli Zaretskii
2022-05-31 13:43 ` Eli Zaretskii
2022-05-31 16:22 ` Akib Azmain Turja
2022-05-31 16:39 ` Eli Zaretskii
2022-05-31 18:11 ` Akib Azmain Turja
2022-05-31 18:30 ` Akib Azmain Turja
2022-05-31 19:22 ` Eli Zaretskii
2022-06-01 1:10 ` Akib Azmain Turja
2022-06-01 2:42 ` Eli Zaretskii
2022-06-01 11:26 ` Akib Azmain Turja
2022-06-01 12:15 ` Eli Zaretskii
2022-06-01 12:41 ` Akib Azmain Turja
2022-06-01 13:03 ` Akib Azmain Turja
2022-06-01 13:13 ` Eli Zaretskii
2022-06-01 13:07 ` Eli Zaretskii
2022-06-01 16:36 ` Akib Azmain Turja
2022-06-01 17:23 ` Eli Zaretskii
2022-06-02 10:52 ` Philip Kaludercic
2022-06-02 16:47 ` Akib Azmain Turja
2022-05-31 14:17 ` Andreas Schwab
2022-05-31 14:23 ` Visuwesh
2022-05-31 16:24 ` Akib Azmain Turja
2022-05-31 14:52 ` Michael Heerdegen
2022-05-31 16:24 ` Akib Azmain Turja
2022-05-31 16:25 ` Akib Azmain Turja
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=YpYZvCfOhIhOVxiE@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-devel@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).