Thank you!
I suspect the braking commit is cfc34f0371df4fff66561016792757bce83a62d1
I checked-out on 63b7cf6febf3f41e59b8803c06994e12a550c46a (which is earlier than the one above), and continued with a successful installation.
I realized that you are pushing new commits every few hours to the master branch of all the opm-modules. I guess these are not all properly unit-tested? How should I proceed to compile a 'stable' executable?
Andres
----- Original message -----
From: Joakim Hove <[email protected]>
To: Andres Codas Duarte <[email protected]>
Cc:
Subject: Re: [Opm] Help with installation
Date: Tue, Aug 1, 2017 6:09 PM
From: Joakim Hove <[email protected]>
To: Andres Codas Duarte <[email protected]>
Cc:
Subject: Re: [Opm] Help with installation
Date: Tue, Aug 1, 2017 6:09 PM
Sorry - I did not read your message properly through. The problem is that the layout of package libecl has changed from multiple libraries, which opm-parser version 2017.04 expects and only one library - which current opm parser expects.
_______________________________________________ Opm mailing list [email protected] http://opm-project.org/cgi-bin/mailman/listinfo/opm
