On Fri, 15 Jan 2016, Willem Jan Withagen wrote: > On 30-11-2015 14:21, Sage Weil wrote: > > The problem with all of the porting code in general is that it is doomed > > to break later on if we don't have (at least) ongoing build tests. In > > order for a FreeBSD or OSX port to continue working we need VMs that run > > either gitbuilder or a jenkins job or similar so that we can tell when it > > breaks. > > > > If someone is willing to run a VM somewhere to do this we can pretty > > easily stick it on the gitbuilder page at > > > > http://ceph.com/gitbuilder.cgi > > Well this is real nice case of such an incident. > > I'm verifying my changes to the C/C++ code, after having forwarded to HEAD. > And now I get bluestore complaining that it requires AIO. > Something I've thusfar excluded in the build. > > Does Bluestore really require AIO?? > FreeBSD does have AIO, but to take simple steps one at the time, I excluded it > with configure. Mainly because it bombs at compile time. Probably due to > different include files, or function nameing..... > > So, in order of preference: > - Can I disable AIO for Bluestore > - Can I disable bluestore being build? AIO is currently required. The good news is it is confined (mostly) to os/bluestore/BlockDevice.h, so providing an alternative (or non-aio) implementaiton shouldnt' be difficult.. in fact it is mostly there. sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
