Closed Hermanverschooten closed 2 years ago
What do which make
and which gcc
return for you? How have you installed them? Do you do something special to add them to your path?
Air-van-Herman➜ ~ which gcc
/usr/bin/gcc
Air-van-Herman➜ ~ which make
/usr/bin/make
There is a gcc
in my brew list
, so I probably installed it that way.
Air-van-Herman➜ ~ which pkg-config
/opt/homebrew/bin/pkg-config
Will this be the cause? I mean /usr/bin
is probably in the PATH
by default, but the homebrew path is not, that is set in .zshrc
.
Yeah, that’s it. I guess we will need a new setting for additional paths?
Yup. The app runs in a very limited environment:
# MyApp.app/Contents/MacOS/MyApp
#!/bin/sh
osascript -e "tell app \"System Events\" to display dialog \"$(env)\""
So yeah, we basically need to manipulate $PATH somehow but worth noting that such notebook is not reproducible, in order to run it we need to run in a specific and implicit build environment. So it's a no-no for sharing but obviously it is an important scenario for just exploring things. For that I think it'd be best to manually adjust $PATH by calling System.put_env("PATH", ...)
before Mix.install call. Would that work?
We're also hoping to see packages not needing build environment thanks to projects like:
That would probable also solve the issue @wojtekmach closed for nmake
on windows #1248 .
@wojtekmach I added
path = System.get_env("PATH")
System.put_env("PATH", path <> ":/opt/homebrew/bin")
That got me further but now it complains it cannot find "erl_nif.h".
Ok lack of erl_nif is a bug, will look into it.
The missing erl_nif.h fix is out in updated release artifacts, thanks again for the report! https://github.com/livebook-dev/livebook/releases/tag/v0.6.3
@wojtekmach Just to confirm that it now does work, thanks!
Environment
git rev-parse HEAD
if running with mix): 0.6.3Current behavior
Evaluating the livebook found at vix gibhub, I get this error:
I thought I missed libvips (a prerequisite), but it is installed.
Expected behavior
I expected it to install/build
:vix
When I use the same Livebook using
livebook server
, it does not have the same issue.