a-maze-d
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 are coming from, to understand what they are used for and whether I might run into problems down the row.
A search for those calls didn’t reveal anything. The library does use some macros, but those should (if my understanding is correct) be resolved at compile time. Of course the issue might come from some transient dependencies.
Is there a good way to figure out where those function calls are coming from?
Thanks for any ideas and help
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security










Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
outlog
well they are definitely from a dep, but that is obvious..
can you try using
MIX_ENV=prodin 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..)a-maze-d
stupid me, should have thought about that one. Let me try that and report back.
Thanks
a-maze-d
Unfortunately that’s not the reason, still the same result.
a-maze-d
I could track them both down with a lot of trial and error. Problem solved
The issues were (in one of the
deps):Macro.escapeinstead ofunquoteCode.loaded?,Code.ensure_loaded?,:code.purge, and:code.delete. Removing that part removed the second warning too.Regarding the first one:
The code looked like the following:
The tricky part is that removing the
ast: astfrom the bind_quoted and doing an explicitunquote(ast)didn’t work. Only by removing the wholebind_quoteddid the trick, i.e. the following worked:outlog
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=prodmake any difference?a-maze-d
no
MIX_ENV=proddid not make any difference. I can share the repo, but will take me a couple of daysoutlog
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 similar to:
Let me know..
a-maze-d
I’ll comment on your PR. That’s probably easier