Yes, I see that. I'm going in a different direction with this: https://github.com/jimfcarroll/mesos-on-alpine Thanks for your help.
On Thu, May 5, 2016 at 10:10 PM, haosdent <[email protected]> wrote: > >fatal error: fts.h: No such file or directory > Could not find this file > > On Fri, May 6, 2016 at 10:02 AM, John Muller <[email protected]> wrote: > > > That gets me through configure, but make fails: > > > > In file included from > > > > > ../../../3rdparty/libprocess/3rdparty/stout/include/stout/os/rmdir.hpp:22:0, > > from > > ../../../3rdparty/libprocess/3rdparty/stout/include/stout/os.hpp:55, > > from ../../../3rdparty/libprocess/src/io.cpp:24: > > > > > ../../../3rdparty/libprocess/3rdparty/stout/include/stout/os/posix/rmdir.hpp:16:17: > > fatal error: fts.h: No such file or directory > > compilation terminated. > > Makefile:830: recipe for target 'libprocess_la-io.lo' failed > > make[4]: *** [libprocess_la-io.lo] Error 1 > > make[4]: Leaving directory '/tmp/mesos-0.28.1/build/3rdparty/libprocess' > > Makefile:1321: recipe for target 'all-recursive' failed > > make[3]: *** [all-recursive] Error 1 > > make[3]: Leaving directory '/tmp/mesos-0.28.1/build/3rdparty/libprocess' > > Makefile:491: recipe for target 'all-recursive' failed > > make[2]: *** [all-recursive] Error 1 > > make[2]: Leaving directory '/tmp/mesos-0.28.1/build/3rdparty' > > make[1]: *** [all] Error 2 > > Makefile:444: recipe for target 'all' failed > > make[1]: Leaving directory '/tmp/mesos-0.28.1/build/3rdparty' > > Makefile:730: recipe for target 'all-recursive' failed > > make: *** [all-recursive] Error 1 > > > > On Thu, May 5, 2016 at 9:18 PM, haosdent <[email protected]> wrote: > > > > > Could it success when you "../configure --disable-java > --disable-python" > > > > > > On Fri, May 6, 2016 at 9:06 AM, John Muller <[email protected]> > > wrote: > > > > > > > Hi All, > > > > > > > > I'm trying to make a small Alpine linux based Docker image for Mesos > > > > 0.28.0; gist is here: > > > > > > > > https://gist.github.com/blue666man/c6ae9b19c01d813e1028898626930667 > > > > > > > > Configure gets to the point where it checks JNI and exits with the > > > > following: > > > > > > > > "checking whether or not we can build with JNI... > > > > > > > > > > > > > > /usr/lib/gcc/x86_64-alpine-linux-musl/5.3.0/../../../../x86_64-alpine-linux-musl/bin/ld: > > > > h_errno: TLS definition in //usr/glibc/usr/lib/libc.so.6 section > .tbss > > > > mismatches non-TLS definition in > > > > //usr/lib/gcc/x86_64-alpine-linux-musl/5.3.0/../../../../lib/libc.so > > > > section .bss > > > > //usr/glibc/usr/lib/libc.so.6: error adding symbols: Bad value > > > > collect2: error: ld returned 1 exit status > > > > configure: error: failed to build with JNI" > > > > > > > > Has anyone run across linker errors using musl before (specifically > > > > non-thread local storage for h_errno)? Package options with Alpine > are > > > > limited; there is no glibc package to use, so I'm hoping for a > > > work-around. > > > > > > > > Thanks, > > > > John > > > > > > > > > > > > > > > > -- > > > Best Regards, > > > Haosdent Huang > > > > > > > > > -- > Best Regards, > Haosdent Huang >
