[Dune] Check for METIS and ParMetis

[Eike Mueller]

Dear Dune-list,

I have a related problem: On Hector the libraries (in the ParMETIS 
directories, i.e. I'm only using ParMETIS and not a separate METIS 
installation) are called libmetis_gnu.a and libparmetis_gnu.a and for 
this reason ParMETIS is not detected at the configure stage. I think I 
can fix this by running autogen and then replace -lmetis and -lparmetis 
in the configure scripts that are generated, but is there a more elegant 
way, e.g. passing arguments to autogen in the configuration file to make 
sure it uses the correct libraries? Or can I edit one of the autogen 
input files?

Thanks a lot,

Eike

PS: I've already asked Hector support whether they can simply rename the 
libraries to libmetis.a and libparmetis.a or create symbolic links, but 
they are reluctant to do this.

Christoph Grüninger wrote:
> Hello everyone,
> I tried to use the checks in dune-common for METIS and ParMETIS. I 
> installed the newest version from [1] followed the install instructions 
> and installed it with prefix=$somewhere.
> With METIS this went fine but the installed ParMETIS does not provide a 
> header metis.h. I cannot use the one from METIS because the result from 
> METIS is not included in the test for ParMETIS.
> BTW in the test for ParMETIS some search paths seems to be false. But 
> even if I change these metis.h is not found.
> Does someone use the tests? What do you different from me?
> 
> I think the tests metis.m4 and parmetis.m4 from ALUGrid 1.50 are nicer 
> then the tests dune-common provides. Especially the metis test is kind 
> of alien to the other Dune tests. What about useing these in dune-common?
> Thou the tests from ALUGrid didn't recognize my ParMETIS installation 
> neither. Maybe ParMETIS changes something in PARMETIS version 4?
> 
> Thanks in advance
> Christoph
> 
> [1] http://glaros.dtc.umn.edu/gkhome/views/metis
>