On 13/11/2018 08:24, Gaudenz Steinlin wrote: > > Hi > > Emilio Pozuelo Monfort <po...@debian.org> writes: >> Your package can no longer be built on several architectures, as >> libboost-context is not built everywhere. Possible solutions would be: >> 1) Make that build-dep optional > > I don't think that's possible. Or do you have any pointers how Ceph could be > built without libboost-context?
There's a pull request here to make boost-context optional for this very same reason: https://github.com/ceph/ceph/pull/15225 > The only option I see going in that direction is to use the embedded copy of > Boost which ships with the Ceph sources. But I'd like to avoid that and I > actually doubt this will build on these architectures if the Boost Debian > package does not build. Yeah that won't work, given ceph requires boost-context, which doesn't work on some architectures. >> 2) Look if that boost library can now be built on more architectures > > Was the boost build disabled on these architectures? I was under the > impression > that we are just missing builds for these and that they will eventually get > done. My time resources to work on other packages are a bit limited. Do you > know > why Boost is not built on these architectures? boost in general builds on those architectures. It's only boost-context that is disabled on some architectures where it doesn't work: libboost-context-dev deb libdevel optional arch=any-i386,any-amd64,armel,armhf,arm64,mips,mipsel,powerpc,ppc64el >> 3) Remove ceph from the affected architectures > > If we can't get this fixed and all the other architectures build fine this is > probably the easiest option. However sad... Let's leave that as the last resort. >> See the affected architectures at >> https://buildd.debian.org/status/package.php?p=ceph > > I'm currently working on the build failures on mips, mipsel and armel. Great! Emilio
