It certainly would. For those not in the loop, e2fsprogs-libuuid is
problematic on FreeBSD because it shadows a symbol defined in libc.
There's a workaround, but boost::uuid would be better.
-Alan
On Sat, Nov 9, 2013 at 9:41 AM, Noah Watkins wrote:
> Alan, would this fix the problem on FreeBSD?
This approach is basically what Kyua did for libc++ compatibility. It
looks good. The only things I don't like are the
CEPH_HASH_NAMESPACE_{START,END} macros. I'm personally not a fan of
macros that change language syntax. However, I can't come up with an
alternative that doesn't involve either
