Hey Chris, thanks for finding that, filed
MESOS-344<https://issues.apache.org/jira/browse/MESOS-344>
.


On Sun, Feb 10, 2013 at 2:49 PM, Mattmann, Chris A (388J) <
[email protected]> wrote:

> [Dropping general@incubator since this is project specific]
>
> Thanks Vinod!
>
> Just as an FYI, I ran the test suite, and got this:
>
> ests-allocator_tests.o `test -f 'tests/allocator_tests.cpp' || echo
> './'`tests/allocator_tests.cpp
> In file included from ./tests/base_zookeeper_test.hpp:30,
>                  from tests/allocator_tests.cpp:33:
> ./jvm/jvm.hpp:4:17: error: jni.h: No such file or directory
> In file included from ./tests/base_zookeeper_test.hpp:30,
>                  from tests/allocator_tests.cpp:33:
> ./jvm/jvm.hpp:94: error: expected Œ,¹ or Œ...¹ before Œid¹
> ./jvm/jvm.hpp:94: error: ISO C++ forbids declaration of ŒjmethodID¹ with
> no type
> ./jvm/jvm.hpp:97: error: ŒjmethodID¹ does not name a type
> ./jvm/jvm.hpp:158: error: expected Œ,¹ or Œ...¹ before Œid¹
> ./jvm/jvm.hpp:158: error: ISO C++ forbids declaration of ŒjmethodID¹ with
> no type
> ./jvm/jvm.hpp:161: error: ŒjmethodID¹ does not name a type
> ./jvm/jvm.hpp:175: error: expected Œ,¹ or Œ...¹ before Œid¹
> ./jvm/jvm.hpp:175: error: ISO C++ forbids declaration of ŒjfieldID¹ with
> no type
> ./jvm/jvm.hpp:178: error: ŒjfieldID¹ does not name a type
> ./jvm/jvm.hpp:197: error: ŒJNI_VERSION_1_1¹ was not declared in this scope
> ./jvm/jvm.hpp:198: error: ŒJNI_VERSION_1_2¹ was not declared in this scope
> ./jvm/jvm.hpp:199: error: ŒJNI_VERSION_1_4¹ was not declared in this scope
> ./jvm/jvm.hpp:200: error: ŒJNI_VERSION_1_6¹ was not declared in this scope
> ./jvm/jvm.hpp:224: error: Œjobject¹ does not name a type
> ./jvm/jvm.hpp:231: error: Œjobject¹ does not name a type
> ./jvm/jvm.hpp:234: error: expected Œ,¹ or Œ...¹ before Œreceiver¹
> ./jvm/jvm.hpp:234: error: ISO C++ forbids declaration of Œjobject¹ with no
> type
> ./jvm/jvm.hpp:242: error: Œjobject¹ does not name a type
> ./jvm/jvm.hpp:243: error: expected Œ,¹ or Œ...¹ before Œobject¹
> ./jvm/jvm.hpp:243: error: ISO C++ forbids declaration of Œjobject¹ with no
> type
> ./jvm/jvm.hpp:244: error: expected Œ,¹ or Œ...¹ before Œobject¹
> ./jvm/jvm.hpp:244: error: ISO C++ forbids declaration of Œjobject¹ with no
> type
> ./jvm/jvm.hpp:247: error: Œjclass¹ does not name a type
> ./jvm/jvm.hpp:249: error: ŒjmethodID¹ does not name a type
> ./jvm/jvm.hpp:256: error: expected Œ,¹ or Œ...¹ before Œreceiver¹
> ./jvm/jvm.hpp:256: error: ISO C++ forbids declaration of Œjobject¹ with no
> type
> ./jvm/jvm.hpp:259: error: expected Œ,¹ or Œ...¹ before Œid¹
> ./jvm/jvm.hpp:259: error: ISO C++ forbids declaration of ŒjmethodID¹ with
> no type
> ./jvm/jvm.hpp:265: error: ISO C++ forbids declaration of ŒJavaVM¹ with no
> type
> ./jvm/jvm.hpp:265: error: expected Œ;¹ before Œ*¹ token
> ./jvm/jvm.hpp:266: error: ISO C++ forbids declaration of ŒJNIEnv¹ with no
> type
> ./jvm/jvm.hpp:266: error: expected Œ;¹ before Œ*¹ token
> ./jvm/jvm.hpp:271: error: expected Œ,¹ or Œ...¹ before Œreceiver¹
> ./jvm/jvm.hpp:271: error: ISO C++ forbids declaration of Œjobject¹ with no
> type
> ./jvm/jvm.hpp:275: error: expected Œ,¹ or Œ...¹ before Œreceiver¹
> ./jvm/jvm.hpp:275: error: ISO C++ forbids declaration of Œjobject¹ with no
> type
> ./jvm/jvm.hpp: In member function ŒT mesos::internal::Jvm::invoke(int)¹:
> ./jvm/jvm.hpp:278: error: Œmethod¹ was not declared in this scope
> ./jvm/jvm.hpp:279: error: Œreceiver¹ was not declared in this scope
> ./jvm/jvm.hpp: In member function ŒT
> mesos::internal::Jvm::invokeStatic(const mesos::internal::Jvm::JMethod&,
> ...)¹:
> ./jvm/jvm.hpp:294: error: Œconst class mesos::internal::Jvm::JMethod¹ has
> no member named Œid¹
> In file included from ./tests/base_zookeeper_test.hpp:32,
>                  from tests/allocator_tests.cpp:33:
> ./tests/zookeeper_server.hpp: At global scope:
> ./tests/zookeeper_server.hpp:74: error: Œjobject¹ does not name a type
> ./tests/zookeeper_server.hpp:78: error: expected Œ,¹ or Œ...¹ before
> Œ_file¹
> ./tests/zookeeper_server.hpp:78: error: ISO C++ forbids declaration of
> Œjobject¹ with no type
> ./tests/zookeeper_server.hpp:94: error: Œjobject¹ does not name a type
> ./tests/zookeeper_server.hpp:95: error: Œjobject¹ does not name a type
> ./tests/zookeeper_server.hpp:96: error: Œjobject¹ does not name a type
> ./tests/zookeeper_server.hpp:101: error: Œjobject¹ does not name a type
> ./tests/zookeeper_server.hpp:103: error: Œjobject¹ does not name a type
> ./tests/zookeeper_server.hpp: In constructor
> Œmesos::internal::test::ZooKeeperServer::TemporaryDirectory::TemporaryDirec
> tory(mesos::internal::Jvm*, const std::string&, int)¹:
> ./tests/zookeeper_server.hpp:80: error: class
> Œmesos::internal::test::ZooKeeperServer::TemporaryDirectory¹ does not have
> any field named Œfile¹
> ./tests/zookeeper_server.hpp:80: error: Œ_file¹ was not declared in this
> scope
> ./tests/zookeeper_server.hpp: In destructor
> Œmesos::internal::test::ZooKeeperServer::TemporaryDirectory::~TemporaryDire
> ctory()¹:
> ./tests/zookeeper_server.hpp:84: error: Œfile¹ was not declared in this
> scope
> make[3]: *** [tests/mesos_tests-allocator_tests.o] Error 1
> make[2]: *** [check-am] Error 2
> make[1]: *** [check] Error 2
> make: *** [check-recursive] Error 1
> [chipotle:~/tmp/apache-mesos-0.10.0-incubating/mesos-0.10.0] mattmann%
>
> Looks like it's still trying to do something with java, even though I
> built with configure --disable-java. Odd. Anyways, no biggie, I'm still
> +1, probably just something going on in my system  or if it isn't, it can
> be fixed in the next release.
>
>
> Cheers,
> Chris
>
>
> On 2/10/13 2:37 PM, "Vinod Kone" <[email protected]> wrote:
>
> >Chris,
> >
> >Worked great! Tried running make test but got:
> >>
> >>
> >> [chipotle:~/tmp/apache-mesos-0.10.0-incubating/mesos-0.10.0] mattmann%
> >> make test
> >> make: *** No rule to make target `test'.  Stop.
> >> [chipotle:~/tmp/apache-mesos-0.10.0-incubating/mesos-0.10.0] mattmann%
> >>
> >> But that's fine since everything else looks great. Awesome!
> >>
> >>
> >We run 'make check' to build and run our test suite.
> >
> >Thanks,
> >Vinod
> >
> >
> >> Cheers,
> >> Chris
> >>
> >>
> >>
> >> On 2/7/13 10:32 PM, "Benjamin Hindman" <[email protected]> wrote:
> >>
> >> >Please vote on releasing the following candidate as Apache Mesos
> >> >(incubating) version 0.10.0. This will be the second incubator release
> >>for
> >> >Mesos in Apache.
> >> >
> >> >
> >>
> >>>------------------------------------------------------------------------
> >>>--
> >> >-------
> >> >Changes since last release candidate:
> >> >  * Updated configure.ac to work better on OS X 10.8.
> >> >  * Added missing license (the only blocker on the previous candidate).
> >>
> >>>------------------------------------------------------------------------
> >>>--
> >> >-------
> >> >
> >> >
> >> >The candidate for Mesos 0.10.0-incubating release is available at:
> >> >
> >> >
> >>
> >>
> http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-i
> >>n
> >> >cubating.tar.gz
> >> >
> >> >The tag to be voted on:
> >> >
> >> >
> >>
> >>
> https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.10.0-incu
> >>b
> >> >ating-RC4
> >> >
> >> >The MD5 checksum of the tarball can be found at:
> >> >
> >> >
> >>
> >>
> http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-i
> >>n
> >> >cubating.tar.gz.md5
> >> >
> >> >The signature of the tarball can be found at:
> >> >
> >> >
> >>
> >>
> http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-i
> >>n
> >> >cubating.tar.gz.asc
> >> >
> >> >Mesos' KEYS file, containing the PGP keys used to sign the release:
> >> >  http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS
> >> >
> >> >Please vote on releasing this package as Apache Mesos
> >>0.10.0-incubating!
> >> >
> >> >The vote is open until Monday, February 11th at 5:00 pm (PST) and
> >>passes
> >> >if
> >> >a majority of at least 3 +1 IPMC votes are cast.
> >> >
> >> >[ ] +1 Release this package as Apache Mesos 0.10.0-incubating
> >> >[ ] -1 Do not release this package because ...
> >> >
> >> >To learn more about Apache Mesos, please see
> >>http://www.mesosproject.org.
> >>
> >>
>
>

Reply via email to