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? BTW, I did a quick check in nightly log and found diffutils and grep have the same issue(but it is minor for them so it didn't break the build) ================= diffutils-2.8.1 log ================== config.status: linking ./lib/regex.hin to lib/regex.h ./config.status: line 1415: cd: HOME not set config.status: executing depfiles commands ./config.status: line 1415: cd: HOME not set config.status: executing default-1 commands config.status: creating po/POTFILES config.status: creating po/Makefile ./config.status: line 1415: cd: HOME not set config.status: executing default commands ========================= end ========================== ===================== grep 2.5 log ===================== config.status: creating config.h ./config.status: line 1148: cd: HOME not set config.status: executing default-1 commands ./config.status: line 1148: cd: HOME not set config.status: executing default-2 commands config.status: creating po/POTFILES config.status: creating po/Makefile ./config.status: line 1148: cd: HOME not set config.status: executing default commands ========================= end ========================== -- Regards, Raymond
