-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make an installation script #4
Labels
enhancement
New feature or request
Comments
guilhermevarela
added a commit
that referenced
this issue
Sep 27, 2019
guilhermevarela
added a commit
that referenced
this issue
Sep 30, 2019
guilhermevarela
added a commit
that referenced
this issue
Sep 30, 2019
guilhermevarela
added a commit
that referenced
this issue
Oct 3, 2019
guilhermevarela
pushed a commit
that referenced
this issue
Oct 8, 2019
guilhermevarela
added a commit
that referenced
this issue
Oct 8, 2019
NOTE: ===== Launch on rnl.sh is not yet supported since some dependencies for running sumo cannot be installed without root priviledge. Two possible workarounds: (a) contact admin (b) deploy with docker. LOG: === These are selected parts from running rnl.sh 1) Can't really use script as there are no sudo permission > Installing system dependencies for SUMO > scripts/setup_sumo_ubuntu1804.sh: line 4: sudo: command not found > scripts/setup_sumo_ubuntu1804.sh: line 5: sudo: command not found > scripts/setup_sumo_ubuntu1804.sh: line 6: sudo: command not found > scripts/setup_sumo_ubuntu1804.sh: line 7: sudo: command not found > scripts/setup_sumo_ubuntu1804.sh: line 8: sudo: command not found > scripts/setup_sumo_ubuntu1804.sh: line 9: sudo: command not found > scripts/setup_sumo_ubuntu1804.sh: line 10: sudo: command not found 2) Paths error Installing sumo binaries ./rnl.sh: line 24: pushd: ilu/sumo_binaries/bin: No such file or directory 3) Dependencies error sumo: error while loading shared libraries: libxerces-c-3.2.so: cannot open shared object file: No such file or directory
guilhermevarela
added a commit
that referenced
this issue
Jan 9, 2020
gsavarela
added a commit
that referenced
this issue
Mar 2, 2020
gsavarela
pushed a commit
that referenced
this issue
Mar 2, 2020
gsavarela
pushed a commit
that referenced
this issue
Mar 2, 2020
gsavarela
added a commit
that referenced
this issue
Mar 2, 2020
gsavarela
added a commit
that referenced
this issue
Mar 2, 2020
gsavarela
added a commit
that referenced
this issue
Mar 2, 2020
gsavarela
added a commit
that referenced
this issue
Mar 2, 2020
gsavarela
added a commit
that referenced
this issue
Mar 2, 2020
gsavarela
pushed a commit
that referenced
this issue
Mar 2, 2020
gsavarela
added a commit
that referenced
this issue
Mar 2, 2020
gsavarela
added a commit
that referenced
this issue
Mar 2, 2020
gsavarela
added a commit
that referenced
this issue
Mar 2, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An installation script is necessary for code-deployment on cluster
Facilitate distribution
The text was updated successfully, but these errors were encountered: