[Dune] Notification from Dune

[Flyspray]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below.

User who did this: - Markus Blatt (mblatt)

Attached to Project - Dune
Summary - build fails in grid/io/file/dgfparser/test
Task Type - Bug Report
Category - Common
Status - New
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - SVN
Due in Version - 
Due Date - Undecided
Details - Currently building dune fails (if no additional grids are
installed):

/bin/sh ../../../../../libtool --tag=CXX --mode=link g++-4.0  -O3
-DNDEBUG -funroll-loops    -o tester  tester-main.o
../../../../../grid/libgrid.la       -L/usr/lib/lam/lib -llammpio
-llamf77mpi -lmpi -llam -lutil -ldl  -L/usr/local/ug/lib -lm
g++-4.0 -O3 -DNDEBUG -funroll-loops -o tester tester-main.o 
../../../../../grid/.libs/libgrid.a -L/usr/lib/lam/lib -llammpio
-llamf77mpi -lmpi -llam -lutil -ldl -L/usr/local/ug/lib -lm
tester-main.o: In function `__tcf_0':
main.cc:(.text+0x8e): undefined reference to `Dune::dvverb'
tester-main.o: In function `Dune::MPIHelper::instance(int&, char**&)':
main.cc:(.gnu.linkonce.t._ZN4Dune9MPIHelper8instanceERiRPPc[Dune::MPIHelper::instance(int&,
char**&)]+0x92): undefined reference to `Dune::dvverb'
tester-main.o: In function `void Dune::checkIndexSetForCodim<0,
Dune::YaspGrid<2, 2>, Dune::IndexSet<Dune::YaspGrid<2, 2> const,
Dune::YaspLevelIndexSet<Dune::YaspGrid<2, 2> const>,
Dune::YaspLevelIndexSetTypes<Dune::YaspGrid<2, 2> const> >,
Dune::DebugStream<1u, 4u, 1u, Dune::greater_or_equal>
>(Dune::YaspGrid<2, 2> const&, Dune::IndexSet<Dune::YaspGrid<2, 2>
const, Dune::YaspLevelIndexSet<Dune::YaspGrid<2, 2> const>,
Dune::YaspLevelIndexSetTypes<Dune::YaspGrid<2, 2> const> > const&,
Dune::DebugStream<1u, 4u, 1u, Dune::greater_or_equal>&, bool)':


This seems to me as if libcommon is needed here. Unfortunately there
is no portable way to specify this.

I am wondering  why this line in Makefile.am is necessary anyway:

# test program for all tpyes of grids
noinst_PROGRAMS = tester 

In my opinion nothing should be build in any test directory when
making a make all.
Could we just skip building tester?

More information can be found at the following URL:
http://hal.iwr.uni-heidelberg.de/flyspray/?do=details&id=189

You are receiving this message because you have requested it from the
Flyspray bugtracking system.  You can be removed from future
notifications by visiting the URL shown above.