Firstly, I'm not familiar with ruby, sbt or scalding and only starting scala... so I m

Are you running on linux with an encrypted home? <a href="https://gr

Problem in compiling on Ubuntu 11.10 about scalding HOT 8 CLOSED

twitter commented on May 15, 2024

Problem in compiling on Ubuntu 11.10

from scalding.

Comments (8)

azymnis commented on May 15, 2024

A couple of questions:

What version of sbt are you running?
Can you try it by changing scala to 2.8.2 and see what happens?

from scalding.

johnynek commented on May 15, 2024

Note, sbt will download the correct version of scala. It does not need to match your system. It will keep it inside the project, and if you don't change the version number of scala, it should work.

That said, 2.9.0.1 might have some issue. I have only tested successfully with 2.8.1 and 2.9.1. Can you try with one of those?

Running with 2.9.1:

sbt clean
sbt update
sbt test

works fine for me. Also with 2.8.1 (2.8.2 doesn't work for me currently, but version fragility is not an uncommon issue with scala, the best I can offer immediately is try to use a version known to work). I'll wrestle with 2.8.2 and try to make it compile also. These are not real bugs, but type issues due to weakly typed (but type parameterized half the time) Cascading.

PS: I am sorry about the deprecation warnings, but hadoop deprecated then undeprecated some files, so the version of cascading uses the code that was, for a a short time, deprecated. It's not pretty, but not much we can easily do from our position.

from scalding.

hgavert commented on May 15, 2024

Hi!

I'm not sure if I'm doing the "running with 2.9.1" correctly, so here are the steps that I did:

$ git clone http://github.com/twitter/scalding.git
$ emacs -nw build.sbt # change 
$ ~/bin/sbt clean

$ ~/bin/sbt update
[info] Loading project definition from /home/me/dev/scala/scalding/project
[info] Set current project to scalding (in build file:/home/me/dev/scala/scalding/)
[info] Updating {file:/home/me/dev/scala/scalding/}default-bc2517...
[info] Resolving org.scala-lang#scala-library;2.9.1 ...
[info] Resolving cascading#cascading-core;2.0.0-wip-165 ...
[info] Resolving riffle#riffle;0.1-dev ...
[info] Resolving org.slf4j#slf4j-api;1.6.1 ...
[info] Resolving thirdparty#jgrapht-jdk1.6;0.8.1 ...
[info] Resolving org.codehaus.janino#janino;2.5.16 ...
[info] Resolving org.slf4j#slf4j-log4j12;1.6.1 ...
[info] Resolving log4j#log4j;1.2.16 ...
[info] Resolving cascading#cascading-local;2.0.0-wip-165 ...
[info] Resolving com.google.guava#guava;10.0.1 ...
[info] Resolving com.google.code.findbugs#jsr305;1.3.9 ...
[info] Resolving cascading#cascading-hadoop;2.0.0-wip-165 ...
[info] Resolving org.apache.hadoop#hadoop-core;0.20.2 ...
[info] Resolving commons-cli#commons-cli;1.2 ...
[info] Resolving xmlenc#xmlenc;0.52 ...
[info] Resolving commons-httpclient#commons-httpclient;3.0.1 ...
[info] Resolving commons-logging#commons-logging;1.0.3 ...
[info] Resolving commons-codec#commons-codec;1.3 ...
[info] Resolving commons-net#commons-net;1.4.1 ...
[info] Resolving oro#oro;2.0.8 ...
[info] Resolving org.mortbay.jetty#jetty;6.1.14 ...
[info] Resolving org.mortbay.jetty#jetty-util;6.1.14 ...
[info] Resolving org.mortbay.jetty#servlet-api-2.5;6.1.14 ...
[info] Resolving tomcat#jasper-runtime;5.5.12 ...
[info] Resolving tomcat#jasper-compiler;5.5.12 ...
[info] Resolving org.mortbay.jetty#jsp-api-2.1;6.1.14 ...
[info] Resolving org.mortbay.jetty#jsp-2.1;6.1.14 ...
[info] Resolving org.eclipse.jdt#core;3.1.1 ...
[info] Resolving ant#ant;1.6.5 ...
[info] Resolving commons-el#commons-el;1.0 ...
[info] Resolving net.java.dev.jets3t#jets3t;0.7.1 ...
[info] Resolving commons-logging#commons-logging;1.1.1 ...
[info] Resolving net.sf.kosmosfs#kfs;0.3 ...
[info] Resolving junit#junit;4.5 ...
[info] Resolving hsqldb#hsqldb;1.8.0.10 ...
[info] Resolving commons-lang#commons-lang;2.4 ...
[info] Resolving de.javakaffee#kryo-serializers;0.9 ...
[info] Resolving com.googlecode#kryo;1.04 ...
[info] Resolving com.googlecode#reflectasm;1.01 ...
[info] Resolving asm#asm;3.2 ...
[info] Resolving com.googlecode#minlog;1.2 ...
[info] Resolving org.scala-tools.testing#specs_2.8.0;1.6.5 ...
[info] Done updating.
[success] Total time: 5 s, completed Feb 10, 2012 9:20:21 AM
$ ~/bin/sbt test
[info] Loading project definition from /home/me/dev/scala/scalding/project
[info] Set current project to scalding (in build file:/home/me/dev/scala/scalding/)
[info] Compiling 18 Scala sources to /home/me/dev/scala/scalding/target/scala-2.9.1/classes...
[warn] there were 20 deprecation warnings; re-run with -deprecation for details
[warn] one warning found
[info] Compiling 8 Scala sources to /home/me/dev/scala/scalding/target/scala-2.9.1/test-classes...
[error] File name too long
[error] one error found
[error] {file:/home/me/dev/scala/scalding/}default-bc2517/test:compile: Compilation failed
[error] Total time: 77 s, completed Feb 10, 2012 9:21:54 AM

BTW, the sbt version is quite likely 0.11.2 (as that is part of the URL for the latest version)

from scalding.

johnynek commented on May 15, 2024

Are you running on linux with an encrypted home?

https://groups.google.com/forum/?fromgroups#!topic/simple-build-tool/wtD6vgdiy6g

This seems like an issue others have had.

"For anyone following this thread, another solution is:

ln -s /tmp project/plugins/target

Not the most ideal, but it seems to be working."

from scalding.

hgavert commented on May 15, 2024

Laptop, so of course I'm running encrypted home. Company laptop, so I would not even have a choice :-(
Reading that makes me wonder about the linux encryption... I'll try that later on and report what happens.

from scalding.

johnynek commented on May 15, 2024

Just to document: you shouldn't need to change the sbt file to build. sbt will download the scala compiler jar you need to compile. So, please just try to run the tests with the existing sbt build file.

If that does not work, please report back. After that we can address the issue of using scald.rb, which does use a scala compiler and needs to match the version used to compile scalding.

from scalding.

johnynek commented on May 15, 2024

I'm closing this issue since it seems to be a problem with Ubuntu encrypted home + sbt.

from scalding.

genspire commented on May 15, 2024

To save some people's time, I wanted to add a comment about my experience with this issue.

With the solution to this problem listed above i.e. using ln -s /tmp project/plugins/target

I received the following error when running sbt update:
/home/prj/build.sbt:1: error: not found: object AssemblyKeys
import AssemblyKeys._
^
[error] Type error in expression

When I used Sullivan's solution (from the same thread) it worked without issue:
mkdir /tmp/myproject-target
cd ~/workspace/myproject
rm -rf target
ln -s /tmp/myproject-target target

Hope this helps

from scalding.

Problem in compiling on Ubuntu 11.10 about scalding HOT 8 CLOSED

Comments (8)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent