Error compiling crc from MacOS

[gualopezb]

Erlang version: 22.1
Elixir version: 1.9.1
crc version: 0.9.2

I'm getting the following error while compiling the dependencies with mix deps.compile:

could not compile dependency :crc, "mix compile" failed. You can recompile this dependency with "mix deps.compile crc", update it with "mix deps.update crc" or clean it with "mix deps.clean crc"
** (Mix) Could not compile with "make" (exit status: 2).
You need to have gcc and make installed. Try running the
commands "gcc --version" and / or "make --version". If these programs
are not installed, you will be prompted to install them.

I have both gcc and make installed and they're added properly in the PATH.

[TattdCodeMonkey]

I'll have to update versions locally to see if I can reproduce this. We use elixir_make to compile so it might be related.

[TattdCodeMonkey]

@gualopezb are you still having this issue?

I am trying to reproduce on OSX 10.14.6 and I'm not seeing any errors. I tried compiling crc standalone, and also using it in another project and compiling with mix deps.compile. Neither case produced any errors with

Erlang version: 22
Elixir version: 1.9.4
crc version: 0.9.2

[TattdCodeMonkey]

I did see this today and mix clean && mix compile --force seemed to resolve it for me, but it was intermittent and didn't make sense as I have both make and gcc installed as well.

Going to leave this open for now.

[Hajto]

https://stackoverflow.com/questions/62822875/elixir-crc-will-not-compile-on-mac-os
Mac OS 10.15.5
Elixir 1.10.4
Erlang 22.3

Cleaning dance does not help.

[elsifaka]

I had this problem on my mac and removing my custom LDFLAGS resolved the issue :-)

asdf-vm/asdf-erlang#110 (comment)

[essn]

I had this issue with:

OSX: 12.0 (Apple M1 Pro)
Erlang: 23.2.6
Elixir: 1.11.3-otp-23

Running mix deps.update crc followed by unset KERL_CONFIGURE_OPTIONS and mix deps.compile worked for me.

[TattdCodeMonkey]

I do not have an M1 Mac (yet anyway) so I can't confirm any fixes there. I don't see any usage of KERL_CONFIGURE_OPTIONS directly, but I think a lot of this comes down to compiling & cross-compiling the NIFs which #37 would resolve. But not sure when I'll get time to put towards pure elixir implementation for everything that is currently supported with the NIFs and then transitioning.