On 06/10/15 11:59, Gaudenz Steinlin wrote: > Emilio Pozuelo Monfort <po...@debian.org> writes: > >> [ explicit Cc's as this goes to a list that seems to be moderated... ] >> >> On Sat, 26 Sep 2015 16:39:46 +0200 Emilio Pozuelo Monfort <po...@debian.org> >> wrote: >>> Can we have this fixed in unstable as well? ceph currently fails to build >>> there >>> and this is blocking various transitions. >> >> This is blocking the boost, icu, libleveldb and libsnappy transitions. I'll >> try >> to look at NMU'ing this if you don't have the time. >> >> FWIW the version in experimental failed to build on armel, so just uploading >> that to sid wouldn't be the best solution... I'd prefer a targeted fix first >> so >> we can finish those transitions. > > I would prefer that too, but I don't have the capacity to port ceph > 0.80.x to libboost1.58. Unless someone can provide a patch I'd go with > just uploading what we have in experimental to unstable.
There's a patch in this bug log, see https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=ceph_0.94.2-2.1.debdiff;bug=795178;att=1 Is that not good enough? > I meant to do some more things before uploading to unstable (like using > the new UIDs for the daemons and proper systemd support), but as it's > blocking other transitions it's better to just upload to unstable soon. > > I'm not sure how to best solve the build failure on armel. Jerasure does > runtime detection of ARM features, so NEON should be enabled for > machines that support it. The error suggests that the -mfloat-abi=softfp > compiler option needs to be set. But I'm not sure if this is the right > thing to do on armel. Some help is needed here. You can ask on the debian-...@lists.debian.org list. Cheers, Emilio
