Hi, I’m trying to build an atomvm image with atomvm.packbeam which gives me the following warnings: Warning: following modules or functions are not available on AtomVM: * Elixir.Macro:escape/1 * elixir_module:compile/6 I’m using an external library and I would like to track down where those calls…

I could track them both down with a lot of trial and error. Problem solved :slight_smile: The issues were (in one of the deps): Wrong use of Macro.escape instead of unquote One module was using some Code.loaded?, Code.ensure_loaded?, :code.purge, and :code.delete. Removing that part removed the s…

well they are definitely from a dep, but that is obvious.. can you try using MIX_ENV=prod in front of the mix call as to consolidate all protocols? (my hunch is we have to enforce MIX_ENV=prod in exatomvm for this very reason..)

stupid me, should have thought about that one. Let me try that and report back. Thanks

Glad you solved it, is that dep public? Either way opened Improve not available warning with path · Issue #67 · atomvm/exatomvm · GitHub as to hopefully be able to improve the warnings.. Did MIX_ENV=prod make any difference?

no MIX_ENV=prod did not make any difference. I can share the repo, but will take me a couple of days

ok, don’t think I need it.. If possible can you try Code warning: show module and function name by petermm · Pull Request #68 · atomvm/exatomvm · GitHub with (the offending code and): {:exatomvm, github: "petermm/ExAtomVM", branch: "add-modules-to-warning", runtime: false}, Should give you output…

I’ll comment on your PR. That’s probably easier

Elixir Programming Language Forum

Narrow down `atomvm.packbeam` warning

Questions & Help Questions

a-maze-d January 24, 2026, 9:03pm 4

Unfortunately that’s not the reason, still the same result.