Compilation issues on AWS #2450
-
Having an issue getting MET to compile fully on an AWS box. Getting the following errors during the ascii2nc portion of the compilation: /usr/bin/ld: ascii2nc-ascii2nc.o: in function Full log file is attached. Any thoughts on what could be the issue? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hello @cwmac, I see you're running into an issue compiling MET version 11.1.0. You're getting undefined references from the linker for ascii2nc. Thanks for sending along the We do most of our development, testing, and common installations of MET with Python embedding enabled. And that has masked this internal library dependency problem that you've uncovered. In fact, I am able to replicate the exact same linker error in ascii2nc when compiling MET 11.1.0 without The workaround is pretty simple. Just follow these instructions to compile support for Python embedding. Set the Thanks for pointing out this problem! I'll write up a bugfix issue for MET version 11.1 and make sure we include a fix in a bugfix release, as well as any future MET releases. |
Beta Was this translation helpful? Give feedback.
-
Hey @JohnHalleyGotway, was able to get MET to compile with the 'enable-python' flag. Thanks for the help! |
Beta Was this translation helpful? Give feedback.
Hello @cwmac, I see you're running into an issue compiling MET version 11.1.0. You're getting undefined references from the linker for ascii2nc.
Thanks for sending along the
make_install.log
file. That makes it much easier to debug. Judging by its contents, I infer that you're configuring/compiling MET without support for Python embedding. So that means that you are not passing the--enable-python
option to the configure script. And that's totally fine, support for Python embedding is optional and is disabled by default. However, I think this compilation error you're getting is due to the fact that--enable-python
is not used.We do most of our development, testing, and common installatio…