#916 aclocal files from non-standard directories are not considered by dune-autogen
Metadata
| Property | Value |
|---|---|
| Reported by | Elias Pipping (elias.pipping@fu-berlin.de) |
| Reported at | May 19, 2011 14:39 |
| Type | Bug Report |
| Version | 2.1 |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Jun 30, 2011 14:43 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Jun 30, 2011 14:43 |
| Closed in version | Unknown |
| Resolution | Not a bug |
| Comment |
Description
When dunecontrol finds an installation of e.g. dune-grid, it should allow dune-autogen to find corresponding files as well.
I have dune-{common,grid,...} installed to a directory below my $HOME, let's called it ${somedir}.
Running
PATH={somedir}/bin:PATH dunecontrol all
for dune-grid-howto fails. That is because macros like DUNE_GRID_CHECKS end up being undefined.
PATH={somedir}/bin:PATH dunecontrol autogen
gives warnings like e.g.
configure.ac:45: warning: DUNE_GRID_CHECK_MODULE is m4_require'd but not m4_defun'd
A workaround is to set ACLOCAL_FLAGS explicitly, thus
ACLOCAL_FLAGS=-I{somedir}/share/aclocal PATH={somedir}/bin/:$PATH dunecontrol all
I think dunecontrol should take care of that by itself, though.
All of this refers to the 2.1 branch of dune; checked out today.