-
Notifications
You must be signed in to change notification settings - Fork 30
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
cant run build_ubuntu.sh file #96
Comments
Did you edit and source Gemenviron first? |
no |
@akrherz so what do i need to edit in the Gemenviron folder |
Please slow the rate of your posts here and take time to look and understand things. There is no |
is there any setup instructions i don't think the old instructions work anymore |
@akrherz ok so when i run tail -f make.out it says make: *** No rule to make target '/subdirs.mk' . Stop. |
you need to edit |
@akrherz i already edited the Gemenviron.profile i added the gempak directory |
/home/awips/Desktop/gempak/gempak |
@awipslinuxuser There are a couple of things that stand out to me about your install... A few comments up you said you set This raises another question though, the It's also standard practice, if not required, to make a symlink to your install directory called I'd recommend going through #57 (comment) and follow those procedures, I can confirm they worked start to finish on a fresh Ubuntu 20.04 LTS install. The other thing you can try is this: https://github.com/whatheway/GEMPAK Another user made a self installer script for installing Gempak on Ubuntu in an attempt to simplify the process. I have not tested this myself, but at a glance it looks like it should work; it was based on the steps linked above. Hope this helps. |
@akrherz when ever i get the app working and installed will i get a interface like this |
That looks like |
Hello, good afternoon, I have problems applying the command |
when i run the ./setup.sh file i get these options
but when i select ubuntu with os_type it gives me a infinite loop i dont know what i did wrong
The text was updated successfully, but these errors were encountered: