Raymond Xiong wrote: > When I used the following way to test my packaging code for > Erlang, I hit an unexpected issue. > > $ env - <path_to_nightly> <env_file> > > Erlang source code contains .c files and .erl files. .c files > are mainly used to compile VM and utilities, which then are > used to compile .erl files. > > Unfortunately those utilities(Erlang runtime actually) requires > HOME directory, but that is unset by "env -" > > I am trying to solve this issue by defining "HOME=/tmp" in > Erlang subdir's Makefile.sfw. But since this is a general > issue caused by "env -" usage, I wonder if anyone has better > suggestion for this? I think we should support "env -" usage, > right? >
You should be able to add any variable to your "new" environment by doing something like this: % env - HOME=<path_to_home> <path_to_nightly> <env_file> & For example: % env - HOME=/export/home/xyz /opt/onbld/bin/nightly sfw-developer.sh &
