Skip to content
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

Error: ‘cmp’ is not a member of ‘ERT::smspec_node’ #1125

Open
rksin8 opened this issue Sep 6, 2017 · 8 comments
Open

Error: ‘cmp’ is not a member of ‘ERT::smspec_node’ #1125

rksin8 opened this issue Sep 6, 2017 · 8 comments

Comments

@rksin8
Copy link

rksin8 commented Sep 6, 2017

Hello,
While building opm-parser with dune, I got an error:‘cmp’ is not a member of ‘ERT::smspec_node’. Would you please tell me how to solve this issue? Thank you in anticipation.
error

@joakim-hove
Copy link
Member

When building the master version of opm-parser you need s quite recent version of libecl, I think that is your problem.

Please install an updated version of libecl from github.com/Statoil/libecl - I assume building of opm-parser will work then.

@rksin8
Copy link
Author

rksin8 commented Sep 9, 2017

Thank you for your reply! libecl installation solved the ERT error but another error occurred with opm-core build:
pppp

@atgeirr
Copy link
Member

atgeirr commented Sep 9, 2017

Looks like some trouble with PETSc, MPI and/or the combination of the two. Since the PETSc code is not used except experimentally it should probably be disabled by default. In your case I am guessing that you have some PETSc installation on your system that is found by the OPM build system, and some insufficiently tested combination of options cause this failure. Do we have an option to explicitly turn off PETSc @jokva or @joakim-hove?

@joakim-hove
Copy link
Member

Do we have an option to explicitly turn off PETSc @jokva or @joakim-hove?

Ehhh - apart from the obvious fact that @rksin8 problems are related to MPI in some way - I am completely at a loss here - sorry.

@atgeirr
Copy link
Member

atgeirr commented Sep 9, 2017

Ehhh - apart from the obvious fact that @rksin8 problems are related to MPI in some way - I am completely at a loss here - sorry.

Yes, but if it is only triggered by the PETSc-using code it need to be MPI's fault?

@joakim-hove
Copy link
Member

Ehhh - apart from the obvious fact that @rksin8 problems are related to MPI in some way - I am completely at a loss here - sorry.

Yes, but if it is only triggered by the PETSc-using code it need to be MPI's fault?

Hehe - seems I knew even less than nothing about the topic. The reason I assumed MPI in some way was at fault here was due to the linker error:

[...] : undefined reference to symbol 'ompi_mpi_comm_self' 

@atgeirr
Copy link
Member

atgeirr commented Sep 9, 2017

Too late on a Saturday to solve this...

@rksin8
Copy link
Author

rksin8 commented Sep 9, 2017

Sorry for the trouble! I removed all old dune installation and did a fresh installation of all (dune+dumux+opm) together. finally, installed successfully!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants