[Dune-devel] multiple module error in dunecontrol

[Christian Engwer]

Hi Andreas,

It seems that your pip installed dune-foo is not really installed, but simply an other source directory.

If you install the module, the dune.module file would show up under $PREFIX/lib/dunecontrol/dune-foo/dune.module

dunecontrol ignores installed modules, if you have a source version
available, but you seem to have the sources twice. It seems your pip
install doesnot actually perform a propser install.

Ciao
Christian


On Sat, Nov 14, 2020 at 07:13:27PM +0000, Dedner, Andreas wrote:
> Hi.
> Hope everyone is well. I'm running into a problem with dunecontrol where I'm unsure
> if the feature I assume holds actually doesn't. I have a source version of a module (so cloned git repo) and the same module already installed (into some local folder). When running dunecontrol I get
> 
>    ERROR: multiple definition of module dune-foo
>    previous defined in:
>      /home/dedner/phasefield/dune-env/lib/dunecontrol/dune-foo/dune.module
>    redefined in:                                                                                                   /tmp/pip-install-dwk6r65v/phasefield/dune-foo/dune.module
> Is this supposed to work and if so how do I get dunecontrol to ignore the installed version and take the source one (at the end I wnt to rerun make install). Some mistake in my setup?
> Thanks
> Andreas