On Sun, Oct 26, 2014 at 12:40 AM, Paul Gevers <elb...@debian.org> wrote: > On 26-10-14 07:37, Vincent Cheng wrote: >>> Anny suggestion for a solution since I have no idea about those >>> other architectures? >> >> Drop the build-dep on openmpi-gcc. >> >> You must make sure that the first build dependency in a set of >> alternative build-deps is always installable, otherwise it's going to >> FTBFS on the buildds (even if it builds fine for you locally). This >> isn't an arch-specific problem if that's what you're concerned about; >> if you had uploaded source+i386 (instead of amd64) packages, the amd64 >> build would have failed on the buildds instead. > > Or, if you want openmpi-gcc to be used on the architectures where it is > available, use the arch syntax in the BD. > > e.g. (untested) > Build-Depends: openmpi-gcc (amd64), libopenmpi-dev (!amd64)
Err, I'm pretty sure the syntax for arch-specific build-deps uses brackets, not parentheses, i.e. openmpi-gcc [amd64] | libopenmpi-dev [!amd64]. Also, openmpi-gcc isn't installable in sid on any arch, including amd64. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
