1 Answer
- Newest
- Most votes
- Most comments
0
@Layhooo2
Since you have the required python version installed already and yet you could run the installation script, I think you may do a restart of the cloud9 environment and then try again
To restart your Cloud9 environment, click on the "Wrench" icon in the top right corner of the Cloud9 IDE. In the "Wrench" menu, select "Restart".
Once your Cloud9 environment has restarted, you can try to install your script. Let me know if helps.
answered a year ago
Relevant content
- asked 2 years ago
- asked 4 months ago
- asked a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Thank you for attempting to help me. @Aravind Vadamalaimuthu
So, when I click "Open in Cloud9" it just gives me the unescapable "AWS Cloud9 Installer" prompt box, and never actually loads Cloud9. I am assuming there is a wrench if cloud9 actually loads? I cannot access this wrench it seems. If I run the installer script manually it runs for a very long time and installs a lot of items.
Do you mean to erase and recreate the environment with my SSH settings?
So far whether I run the script manually or automatically, the "AWS Cloud9 Installer" prompt appears regardless when I click "Open in Cloud9".
Here are the final lines of running the script manually:
:Compiling tmux... :Configuring Tmux checking for a BSD-compatible install... /opt/local/bin/ginstall -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /opt/local/bin/gmkdir -p checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking build system type... x86_64-apple-darwin22.1.0 checking host system type... x86_64-apple-darwin22.1.0 checking for gcc... gcc checking whether the C compiler works... no configure: error: in `/Users/<Name>/.c9/tmux-2.2'.
configure: error: C compiler cannot create executables.
See `config.log' for more details