Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gradle build fails with 'Could not load FFI Provider ..' on Windows #2108

Closed
ropley opened this issue Oct 22, 2015 · 5 comments
Closed

gradle build fails with 'Could not load FFI Provider ..' on Windows #2108

ropley opened this issue Oct 22, 2015 · 5 comments
Assignees
Labels
bug build Changes to DITA-OT build scripts platform-dependent Label is obsolete, use specific platform label instead
Milestone

Comments

@ropley
Copy link

ropley commented Oct 22, 2015

Cloned the develop repository, updated the submodules and ran ./gradlew. I got the error below. Googling suggests its a jruby configuration problem but I'm not clear about how jruby is configured for this project.

$ ./gradlew
:compileJava 
warning: [options] bootstrap class path not set in conjunction with -source 1.7
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details. 
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
... some lines skipped
ERROR:  Loading command: install (LoadError)
Could not load FFI Provider: (NotImplementedError) FFI not available: null
See http://jira.codehaus.org/browse/JRUBY-4583
ERROR:  While executing gem ... (NoMethodError)
undefined method `invoke_with_build_args' for nil:NilClass
                                                                           :
html5:compassCompile                                                           FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':html5:compassCompile'.
> Process 'command 'C:\Program Files\Java\jdk1.8.0_40\bin\java.exe'' finished wi
th non-zero exit value 1
@jelovirt jelovirt added the platform-dependent Label is obsolete, use specific platform label instead label Oct 22, 2015
@ropley
Copy link
Author

ropley commented Oct 22, 2015

... it works fine on Linux :0)

@ropley ropley closed this as completed Oct 22, 2015
@ropley ropley reopened this Oct 22, 2015
@eerohele
Copy link

This is a problem with the Gradle Compass plugin. See robfletcher/gradle-compass#37 and robfletcher/gradle-compass#39.

This comment suggests a workaround.

@jelovirt
Copy link
Member

Can someone with Windows test the workaround in OT's gradle configuration and verify it would work?

@jelovirt jelovirt added bug build Changes to DITA-OT build scripts labels Oct 23, 2015
@eerohele
Copy link

Can someone with Windows test the workaround in OT's gradle configuration and verify it would work?

Works for me.

@jelovirt
Copy link
Member

@eerohele could you fix and push to develop directly, no PR needed.

@jelovirt jelovirt added this to the 2.2 milestone Oct 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug build Changes to DITA-OT build scripts platform-dependent Label is obsolete, use specific platform label instead
Projects
None yet
Development

No branches or pull requests

3 participants