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

Xiangrui Meng edited comment on SPARK-5669 at 2/19/15 7:43 PM:
---------------------------------------------------------------

Yes, we are going to remove JBLAS anyway in 1.4. Having a simple dependency 
tree is always a good thing. The problem is how we should proceed for 
branch-1.0/1.1/1.2. If we are covered by this exemption, maybe the only thing 
we need to do is to put a notice. This also applies to branch-1.3. We don't 
call native routines in Spark but it doesn't mean that users don't. With the 
current solution, users need to supply the origin JBLAS jar at runtime to use 
native routines, and I haven't tested whether it works or not. So if we are 
covered by this exemption, the best thing to do might be to revert the patch 
and put a notice.


was (Author: mengxr):
Yes, we are going to remove JBLAS anyway in 1.4. Having a simple dependency 
tree is always a good thing. The problem is how we should proceed for 
branch-1.0/1.1/1.2. If we are covered by this exemption. Maybe the only thing 
we need to do is to put a notice. This also applies to branch-1.3. We don't 
call native routines in Spark but it doesn't mean that users don't. With the 
current solution, users need to supply the origin JBLAS jar at runtime to use 
native routines, and I haven't tested whether it works or not. So if we are 
covered by this exemption, the best thing to do might be to revert the patch 
and put a notice.

> Spark assembly includes incompatibly licensed libgfortran, libgcc code via 
> JBLAS
> --------------------------------------------------------------------------------
>
>                 Key: SPARK-5669
>                 URL: https://issues.apache.org/jira/browse/SPARK-5669
>             Project: Spark
>          Issue Type: Bug
>          Components: Build
>            Reporter: Sean Owen
>            Assignee: Sean Owen
>            Priority: Blocker
>             Fix For: 1.3.0
>
>
> Sorry for "Blocker", but it's a license issue. The Spark assembly includes 
> the following, from JBLAS:
> {code}
> lib/
> lib/static/
> lib/static/Mac OS X/
> lib/static/Mac OS X/x86_64/
> lib/static/Mac OS X/x86_64/libjblas_arch_flavor.jnilib
> lib/static/Mac OS X/x86_64/sse3/
> lib/static/Mac OS X/x86_64/sse3/libjblas.jnilib
> lib/static/Windows/
> lib/static/Windows/x86/
> lib/static/Windows/x86/libgfortran-3.dll
> lib/static/Windows/x86/libgcc_s_dw2-1.dll
> lib/static/Windows/x86/jblas_arch_flavor.dll
> lib/static/Windows/x86/sse3/
> lib/static/Windows/x86/sse3/jblas.dll
> lib/static/Windows/amd64/
> lib/static/Windows/amd64/libgfortran-3.dll
> lib/static/Windows/amd64/jblas.dll
> lib/static/Windows/amd64/libgcc_s_sjlj-1.dll
> lib/static/Windows/amd64/jblas_arch_flavor.dll
> lib/static/Linux/
> lib/static/Linux/i386/
> lib/static/Linux/i386/sse3/
> lib/static/Linux/i386/sse3/libjblas.so
> lib/static/Linux/i386/libjblas_arch_flavor.so
> lib/static/Linux/amd64/
> lib/static/Linux/amd64/sse3/
> lib/static/Linux/amd64/sse3/libjblas.so
> lib/static/Linux/amd64/libjblas_arch_flavor.so
> {code}
> Unfortunately the libgfortran and libgcc libraries included for Windows are 
> not licensed in a way that's compatible with Spark and the AL2 -- LGPL at 
> least.
> It's easy to exclude them. I'm not clear what it does to running on Windows; 
> I assume it can still work but the libs would have to be made available 
> locally and put on the shared library path manually. I don't think there's a 
> package manager as in Linux that would make it easily available. I'm not able 
> to test on Windows.
> If it doesn't work, the follow-up question is whether that means JBLAS has to 
> be removed on the double, or treated as a known issue for 1.3.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to