severity 850559 serious thanks On Thu, 19 Jan 2017, Graham Inggs wrote:
> On 19/01/2017 13:59, Santiago Vila wrote: > > That would be somewhere in debian/rules (in dh_auto_build) for the affected > > packages? > > Or somewhere else? > > Yes, just add 'export OMPI_MCA_rmaps_base_oversubscribe=1' near the top of > debian/rules. > > Most MPI programs should already have 'export > OMPI_MCA_plm_rsh_agent=/bin/false' somewhere, so just below that line would be > fine. > > Would you please confirm that this fix works for one of the affected packages > on your setup? Sorry, my setup is only ready to test packages in the archive (testing or unstable). I will gladly test any package which is uploaded for unstable. Dear openmpi people and interested parties: please do agree on the right fix for this, either following the route suggested by Ansgar when he reassigned this to openmpi-bin or by adding a few lines to the debian/rules file of affected packages, as suggested by Graham. Graham, if you truly think adding a variable is better, please act accordingly and reassign back to the affected packages. In either case I'm setting this to serious again because it makes packages to fail on single-CPU systems, and having more than one CPU is definitely *not* part of the build-essential definition. Thanks.