[ 
https://issues.apache.org/jira/browse/MESOS-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168704#comment-13168704
 ] 

Andy Konwinski commented on MESOS-103:
--------------------------------------

And Charles's response in the email thread quoted in the description of this 
JIRA issue:

<quote>
Configuring with no options is known not to work currently. (This should
be fixed when MESOS-58 is.) We suggest using or modifying one of the
configure.template scripts instead.

It looks like src/Makefile.in can't actually build without Java (at
least because 'all' unconditionally depends on 'java', which
unconditionally depends upon $(MESOS_JAVA_LIB_OBJ), which aren't likely
to build without some JNI headers), which is a bug. (The patch for
MESOS-58 should fix this bug, but it also does a whole bunch of other
things.)
</quote>
                
> Running ./configure without flags fails
> ---------------------------------------
>
>                 Key: MESOS-103
>                 URL: https://issues.apache.org/jira/browse/MESOS-103
>             Project: Mesos
>          Issue Type: Bug
>          Components: build
>         Environment: Linux or OS X
>            Reporter: Andy Konwinski
>            Priority: Blocker
>
> Description of problem from 
> http://mail-archives.apache.org/mod_mbox/incubator-mesos-dev/201112.mbox/%[email protected]%3E
> <quote>
> We configured mesos master branch with no options and while trying to make 
> it, we get the following error...
> ./configure
> make
> .
> .
> .
> .
> g++ -O2 -fno-strict-aliasing -fPIC  -g -I. -I. -I../include -I../include 
> -I../third_party/boost-1.37.0 -I../third_party/protobuf-2.3.0/src 
> -I../third_party/glog-0.3.1/src -I../third_party/glog-0.3.1/src 
> -I../third_party/leveldb/include -I../third_party/libprocess/include -MMD -MP 
> -o ../bin/mesos-getconf configurator/get_conf.cpp common/fatal.o 
> common/lock.o detector/detector.o detector/url_processor.o 
> configurator/configurator.o common/logging.o common/date_utils.o 
> common/resources.o common/utils.o mesos.pb.o messages/messages.pb.o 
> messages/log.pb.o  -L../third_party/protobuf-2.3.0/src/.libs 
> -L../third_party/glog-0.3.1/.libs -L../third_party/leveldb 
> -L../third_party/libprocess 
> -L../third_party/libprocess/third_party/libev-3.8/.libs  -lprotobuf -lglog 
> -lleveldb -lprocess -lev -lpthread -ldl
> g++ -O2 -fno-strict-aliasing -fPIC  -g -I. -I. -I../include -I../include 
> -I../third_party/boost-1.37.0 -I../third_party/protobuf-2.3.0/src 
> -I../third_party/glog-0.3.1/src -I../third_party/glog-0.3.1/src 
> -I../third_party/leveldb/include -I../third_party/libprocess/include -MMD -MP 
> -o ../bin/mesos mesos/main.cpp common/fatal.o common/lock.o 
> detector/detector.o detector/url_processor.o configurator/configurator.o 
> common/logging.o common/date_utils.o common/resources.o common/utils.o 
> mesos.pb.o messages/messages.pb.o messages/log.pb.o  
> -L../third_party/protobuf-2.3.0/src/.libs -L../third_party/glog-0.3.1/.libs 
> -L../third_party/leveldb -L../third_party/libprocess 
> -L../third_party/libprocess/third_party/libev-3.8/.libs  -lprotobuf -lglog 
> -lleveldb -lprocess -lev -lpthread -ldl
> g++ -c -O2 -fno-strict-aliasing -fPIC  -g -I. -I. -I../include -I../include 
> -I../third_party/boost-1.37.0 -I../third_party/protobuf-2.3.0/src 
> -I../third_party/glog-0.3.1/src -I../third_party/glog-0.3.1/src 
> -I../third_party/leveldb/include -I../third_party/libprocess/include -MMD -MP 
> -Ijava/jni -I/include -I/include/linux -I -o java/jni/convert.o 
> java/jni/convert.cpp
> g++: java/jni/convert.o: No such file or directory
> make[1]: *** [java/jni/convert.o] Error 1
> make[1]: Leaving directory `/home/princeton_ram/mesos/src'
> make: *** [src] Error 2
> </quote>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to