Emacs Native Compilation Warnings Popping Up

How to fix it

Try these in order — the most common fix is first.

1. 1. Silence the warnings

   Copy steps
   1. Add (setq native-comp-async-report-warnings-errors nil) to early-init.el or init.el
   2. Restart Emacs
   Did this fix it? Yes No

2. 2. Disable background native compilation

   Copy steps
   1. Set native-comp-deferred-compilation to nil in early-init.el
   2. Packages will use byte-compiled code instead
   Did this fix it? Yes No

3. 3. Let it finish

   Copy steps
   1. Leave Emacs open until the first compile run finishes
   2. Report real warnings to the package maintainer
   Did this fix it? Yes No

Symptoms

*Warnings* or *Async-native-compile-log* buffers keep appearing, with messages about undefined functions or free variables in third-party packages, plus CPU and memory use after launch.

Why it happens

• Native compilation is on by default in newer Emacs builds
• Packages have real warnings that were never visible before with byte-compilation
• Compilation of many packages happens on first launch after install or upgrade

This guide also covers

• emacs native compilation warnings
• emacs async-native-compile-log
• emacs comp warnings

Other GNU Emacs errors

• Emacs Failed to Verify Signature (ELPA Package Install Error)
• Emacs Slow Startup
• Emacs Slow or Freezing With Large Files
• Emacs Eglot / LSP Not Working
• Emacs macOS Operation Not Permitted (Documents, Desktop, iCloud)
• Doom Emacs Errors After Update or doom sync
• Emacs package-install Fails (Package Not Found or Archive Error)