Hacking Freedom: Compiling GNU Emacs from Source

# maker sure to have Git
sudo apt update
sudo apt upgrade

sudo apt install git

cd ~/Fork # or wherever
git clone https://git.savannah.gnu.org/git/emacs.git emacs-build
cd emacs-build

Depending on the compilation options we choose, we need some build and compile time dependencies. Before we can shape the metal, we need the furnace. For example in Debian we need things like:

sudo apt update
sudo apt install build-essential autoconf imagemagick libmagickwand-dev libgtk-3-dev librsvg2-dev libsqlite3-dev libgccjit0 libgccjit-15-dev libgnutls28-dev libtree-sitter-dev

Run the autogen.sh the first time This script will generate the configuration scaffold. You only really need to do this once (and I always forget about it for this very reason). Simply do this on the command line:

./autogen.sh It checks that you have all you need to get started and prints output like this:

Checking whether you have the necessary tools...
(Read INSTALL.REPO for more details on building Emacs)
Checking for autoconf (need at least version 2.65) ... ok
Your system has the required tools.
Building aclocal.m4 ...
Running 'autoreconf -fi -I m4' ...
Building 'aclocal.m4' in exec ...
Running 'autoreconf -fi' in exec ...
Configuring local git repository...
'.git/config' -> '.git/config.~1~'
git config transfer.fsckObjects 'true'
git config diff.cpp.xfuncname '!^[ 	]*[A-Za-z_][A-Za-z_0-9]*:[[:space:]]*($|/[/*])
^((::[[:space:]]*)?[A-Za-z_][A-Za-z_0-9]*[[:space:]]*\(.*)$
^((#define[[:space:]]|DEFUN).*)$'
git config diff.elisp.xfuncname '^\([^[:space:]]*def[^[:space:]]+[[:space:]]+([^()[:space:]]+)'
git config diff.m4.xfuncname '^((m4_)?define|A._DEFUN(_ONCE)?)\([^),]*'
git config diff.make.xfuncname '^([$.[:alnum:]_].*:|[[:alnum:]_]+[[:space:]]*([*:+]?[:?]?|!?)=|define .*)'
git config diff.shell.xfuncname '^([[:space:]]*[[:alpha:]_][[:alnum:]_]*[[:space:]]*\(\)|[[:alpha:]_][[:alnum:]_]*=)'
git config diff.texinfo.xfuncname '^@node[[:space:]]+([^,[:space:]][^,]+)'
Installing git hooks...
'build-aux/git-hooks/commit-msg' -> '.git/hooks/commit-msg'
'build-aux/git-hooks/pre-commit' -> '.git/hooks/pre-commit'
'build-aux/git-hooks/prepare-commit-msg' -> '.git/hooks/prepare-commit-msg'
'build-aux/git-hooks/post-commit' -> '.git/hooks/post-commit'
'build-aux/git-hooks/pre-push' -> '.git/hooks/pre-push'
'build-aux/git-hooks/commit-msg-files.awk' -> '.git/hooks/commit-msg-files.awk'
'.git/hooks/applypatch-msg.sample' -> '.git/hooks/applypatch-msg'
'.git/hooks/pre-applypatch.sample' -> '.git/hooks/pre-applypatch'

You can now run ./configure Do not be intimidated by it. Focus on the final line instead, which directs you to the configure directive.

This is where you sculpt Emacs to your exact workflow. True hackers audit their build environment—you can inspect every configuration option available by running ./configure --help.

For a modern, highly optimized, Wayland-native hacker workstation, these choices are optimal:

./configure --with-native-compilation=aot \
            --with-tree-sitter \
            --with-pgtk \
            --with-dbus \
            --with-imagemagick \
            --with-mailutils

--with-native-compilation=aot

Compiles Emacs Lisp directly into native machine code Ahead-Of-Time. Maximum performance, zero lag.

--with-tree-sitter

Swaps out old regex parsing for high-performance, incremental AST parsing. Better structural navigation and syntax awareness.

--with-pgtk

Pure GTK. Critical if you are running a modern Wayland compositor and want to bypass the legacy Xwayland translation layer completely.

First, ensure you are starting from a completely pristine state. If you are rebuilding an older tree or updating a previous commit, wipe away old compilation artifacts:

make clean

Now, unleash the compiler. Instead of hardcoding an arbitrary job number, let’s query your machine to leverage every single parallel thread your processor has to offer:

make -j$(nproc)

Once the compilation wraps up successfully, verify your creation in-place before deploying it system-wide:

./src/emacs --version

You should be greeted by that glorious declaration of software liberty:

GNU Emacs 31.0.50
Copyright (C) 2026 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GNU Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.

If everything looks pristine, purge any pre-packaged, stale distro binaries and inject your custom-built system into the local environment:

sudo apt remove emacs
sudo make install

Do a final check to confirm your shell path resolves directly to your new build:

which emacs
emacs --version

A good hacker respects filesystem layout and modularity. Do not delete this build directory. Keeping this folder intact ensures you retain the local blueprint of your installation. If you ever want to upgrade to a newer upstream commit or cleanly purge this build from your system, simply navigate back here and run:

sudo make uninstall

Your operating environment remains clean, untainted, and completely under your control. Welcome to the bleeding edge. Happy hacking! 🚀