04-16-2016, 03:12 PM
(04-16-2016, 02:40 PM)ggaliens Wrote: Make sure that ERL_LIBS and export have the proper level of visibility throughout your shells and build session.
I had min in my .profile
so that when I started a new shell. It would get defined. Then I tried putting it in my launch script and somehow that was not as good as doing it in the console windows, or in the .profile
Even with my .profile looking like this:
Code:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.
# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
ERL_LIBS="/home/<user>"
export ERL_LIBS
Code:
escript tools/verify_language_files .
escript tools/release
error:{badmatch,{error,badarg}} in [{release__escript__1460__819428__583980__2,
copy_app,2,
[{file,"tools/release"},{line,178}]},
{release__escript__1460__819428__583980__2,
'-release_otp/1-lc$^0/1-0-',2,
[{file,"tools/release"},{line,141}]},
{release__escript__1460__819428__583980__2,
release_otp,1,
[{file,"tools/release"},{line,141}]},
{release__escript__1460__819428__583980__2,
unix_release,2,
[{file,"tools/release"},{line,82}]},
{release__escript__1460__819428__583980__2,
main,1,
[{file,"tools/release"},{line,22}]},
{escript,run,2,
[{file,"escript.erl"},{line,757}]},
{escript,start,1,
[{file,"escript.erl"},{line,277}]},
{init,start_it,1,[]}]