[Dune] [Dune-Commit] dune-common r6597 - in branches/cmake: . dune/common/test

[Christian Engwer]

On Sun, Mar 25, 2012 at 07:16:54PM +0200, Markus Blatt wrote:
> Hi,
> 
> Are you sure that you do not need any fortran libs?
> How do you get the linker flags without having a fortran compiler?

I want to link from C++, so how does it help if I have a fortran
compiler? If I want to link a fortran lib I need to know the
mangling. The reason to use the fortran compiler is to generate some
dummy code which I can then check for the used mangling.

Christian

> Markus
> On Sun, Mar 25, 2012 at 06:48:24PM +0200, Christian Engwer wrote:
> > On Sun, Mar 25, 2012 at 06:34:24PM +0200, mblatt at dune-project.org wrote:
> > > Author: mblatt
> > > Date: 2012-03-25 18:34:24 +0200 (Sun, 25 Mar 2012)
> > > New Revision: 6597
> > > 
> > > Modified:
> > >    branches/cmake/CMakeLists.txt
> > >    branches/cmake/config.h.cmake
> > >    branches/cmake/dune/common/test/CMakeLists.txt
> > > Log:
> > > Added Lapack test. (Yes, we have to activate Fortran to find out the name mangling!)
> > 
> > actually we don't have to. I have already considered adapting this
> > test for the automake system.
> > 
> > If we install different fortran libs, it might even happen that they
> > have different mangling schemes, if different compilers were used. So
> > I'd add lib-specific mangling info to the buildsystem. When doing so,
> > we could just try different manglings with the usual c-compiler to
> > find the lib specific symbol.
> > 
> > Christian
> > 
> > _______________________________________________
> > Dune mailing list
> > Dune at dune-project.org
> > http://lists.dune-project.org/mailman/listinfo/dune
> > 
> 
> -- 
> Do you need more support with DUNE or HPC in general? 
> 
> Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de
> Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany
> Tel.: +49 (0) 160 97590858  Fax: +49 (0)322 1108991658 
>