Then what if we do not provide native binary convenience artifacts and instead print an INFO level log message, should they be missing, which points to a book chapter on compiling and installing them?
On Wed, Apr 3, 2013 at 10:43 AM, Stack <[email protected]> wrote: > On Wed, Apr 3, 2013 at 10:11 AM, Todd Lipcon <[email protected]> wrote: > > > Shipping the native libs is difficult anyway, because the artifacts will > > depend on the particular architecture/OS that you compile on. (eg if you > > compile on Ubuntu 12.04, it'll be useless on RHEL6 or vice versa). > > > > If we want them to work out of the box, we'd need to cross-compile or > > otherwise do the native lib compile on a number of different slaves and > > collapse them back down into a single dist tarball. > > > > > Thanks Todd. Yeah, the libs made on my mac build box won't be too > generally useful. > > A cross-compile project as part of packaging will be a bit of an > undertaking. Currently, the only native code we ship is the mlockall > support (http://hbase.apache.org/book.html#mlockall). > > St.Ack > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
