-
Notifications
You must be signed in to change notification settings - Fork 4
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
How to install nceplibs-wrf_io on Linux machine? #39
Comments
Please post the full output of cmake and make. |
Here are the files I found in the cmake directory - I copied them into txt files. And here is the Makefile from the top directory -- I copied it into a txt file Here is the Makefile2 from the CMakeFiles directory -- I copied it into a txt file Thank you. |
What I need you to do is try to do the build, and then cut and paste the screen which will include both the commands you used, and the output you got back. For example, here's how it works for me:
|
Here is what I got.
|
Your output says: Build files have been written to: /st6/bayu/opt/NCEPLIBS-wrf_io-1.2.0 But that is not the directory you indicate you are in: [bayu@stratus build]$ cmake -DCMAKE_INSTALL_PREFIX=/st6/bayu/opt .. && make && sudo make install What directory are you in when you issue the cmake command? |
I issued the cmake command in this directory |
Are you sure? Mine says: Yours says: Where's the /build? |
I am sure it is in /build. I typed
|
Sorry I was stumped at the time but rereading this, could it be that your build directory is not a subdirectory of /st6/bayu/opt/NCEPLIBS-wrf_io-1.2.0? |
Hello. I am trying to install nceplibs-wrf_io on our linux machine. Following the "build" instruction, I have done
cmake -DCMAKE_INSTALL_PREFIX=/st6/bayu/opt ..
. Then it prompted.-- Build files have been written to: /st6/bayu/opt/NCEPLIBS-wrf_io-1.2.0
.Then to install it, I tried
make
but it generated errormake: *** No targets specified and no makefile found. Stop.
Could you please advise me on how to install the package in our library?The text was updated successfully, but these errors were encountered: