Steve, It was indeed a protocol buffers issue. I am able to build spark now. Thanks.
On Mon, Jun 29, 2015 at 7:37 AM, Steve Loughran <ste...@hortonworks.com> wrote: > > On 29 Jun 2015, at 11:27, Iulian Dragoș <iulian.dra...@typesafe.com> > wrote: > > > > On Mon, Jun 29, 2015 at 3:02 AM, Alessandro Baretta <alexbare...@gmail.com > > wrote: > >> I am building the current master branch with Scala 2.11 following these >> instructions: >> >> >> > >> Type :help for more information. >> 15/06/29 00:42:20 ERROR ActorSystemImpl: Uncaught fatal error from thread >> [sparkDriver-akka.remote.default-remote-dispatcher-6] shutting down >> ActorSystem [sparkDriver] >> java.lang.VerifyError: class akka.remote.WireFormats$AkkaControlMessage >> overrides final method >> getUnknownFields.()Lcom/google/protobuf/UnknownFieldSet; >> at java.lang.ClassLoader.defineClass1(Native Method) >> at java.lang.ClassLoader.defineClass(ClassLoader.java:800) >> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) >> at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) >> at java.net.URLClassLoader.access$100(URLClassLoader.java:71) >> at java.net.URLClassLoader$1.run(URLClassLoader.java:361) >> at java.net.URLClassLoader$1.run(URLClassLoader.java:355) >> at java.security.AccessController.doPrivileged(Native Method) >> at java.net.URLClassLoader.findClass(URLClassLoader.java:354) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:425) >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:358) >> at >> akka.remote.transport.AkkaPduProtobufCodec$.constructControlMessagePdu(AkkaPduCodec.scala:231) >> at >> akka.remote.transport.AkkaPduProtobufCodec$.<init>(AkkaPduCodec.scala:153) >> at >> akka.remote.transport.AkkaPduProtobufCodec$.<clinit>(AkkaPduCodec.scala) >> at akka.remote.EndpointManager$$anonfun$9.apply(Remoting.scala:733) >> at akka.remote.EndpointManager$$anonfun$9.apply(Remoting.scala:703) >> >> What am I doing wrong? >> >> > > > oh, that's just the version of the protoc protobuf compiler generating > code that implementation classes aren't compatible with, and/or the version > of probuf.jar on the classpath. Google's libraries are turning out to be > surprisingly brittle that way. > > when you type protoc --version on the command line, you should expect to > see, "libprotoc 2.5.0'; and have protobuf-2.5.0 on the classpath. If > neither of those conditions are met: fix them > > -Steve > >
