Closed elbow-jason closed 4 years ago
This appears to have been something an issue with asdf.
I switched asdf's erlang to a different version and back again. Now the includes directory is actually there.
I was using Ash which uses this library and I came across this error on MacOS Mojave.
When I ran make directly as CC='gcc -m32' make
it compiled. Not sure if this is the correct approach.
Setting -m32
is going to compile the library as 32-bit, which you almost certainly don't want if you are compiling on a 64-bit machine. I'm honestly a bit surprised it even works when linked against Erlang.
If you are seeing the same error as originally reported here, it is because the symbols this library links against are missing - which essentially means the libraries we expect to link against cannot be found, which can be for a variety of reasons.
In the case of the original error report, the Erlang installation seemed to be missing the libraries entirely, but it is also possible that we are unable to detect the correct path, and so you may need to set LDFLAGS
or LD_LIBRARY_PATH
to ensure they can be found. If you look at the command string that make
outputs when it invokes the compiler, you'll see what paths are being searched.
Thanks! Yeah, I figured that can't be right. Anyway, I did some digging and discovered my LDFLAGS
was whacked. It's working now!
If anyone stumbles upon this again (like I did), this resolved my issue: https://github.com/bitwalker/picosat_elixir/issues/5#issuecomment-967782411 with CPPFLAGS
and LDFLAGS
.
Building
picosat_elixir
as a dep of another project with{:picosat_elixir, "~> 0.1.1"}
works fine.However, when cloning master and attempting to run tests I see this error:
It's the same error for
iex -S mix
.