Bug#573187: transition: mpi-defaults
On 23/03/10 at 19:11 +0100, Manuel Prinz wrote:
> Am Samstag, den 20.03.2010, 14:01 +0100 schrieb Marc 'HE' Brockschmidt:
> > Manuel Prinz <manuel@debian.org> writes:
> > > This would enable to fix these in a timely fashion. I could start
> > > doing that tomorrow night. How does that sound to you?
> >
> > Sounds good. Sorry for my delayed answer :-/
>
> No problem, same here!
>
> I do not have everything sorted out yet but the issues seem to arise
> from broken assumptions on where MPI stuff may reside. This is trivial
> to fix in some cases and harder in others.
>
> As an example, apbs expects {include,lib} in the same directory, which
> is not the case for mpich2 currently. Lucas, do you think we should
> "fix" this by providing this layout in the MPI -dev packages
> under /usr/lib/{openmpi,mpich2}/? It seems that apbs is not the only
> package assuming this but I did not generate numbers on that. It might
> be worth to have some consistency here nevertheless, IMHO.
Given the low number of packages that FTBFS with mpich2 as mpi-default,
I would say that this could be fixed in the failing packages' build
system, no?
"Fixing" that my providing symlinks might cause subtle failures later,
when the package is actually used and thinks that the libs are in some
place while they aren't.
--
| Lucas Nussbaum
| lucas@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr GPG: 1024D/023B3F4F |
Reply to: