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

Uwe Schindler commented on SOLR-15520:
--------------------------------------

Docker is also not easy useable and is a HUGE dependency not installed on any 
system by default. IMHO, the whole Solr build system should use Gradle and a 
Java VM only, so the current setup looks perfect.

bq. Thanks Uwe for unblocking the situation, and sorry for the trouble it 
caused you.

It was not my local computer, the problem was that Windows builds did not work 
anymore. Jenkins reported this, but nobody was looking into it. So I tried to 
resolve the issues. I know of many customers using Solr in Windows Server, so 
we should not drop it. To test Solr on Windows, you need a working build system 
there, so it should run without installing any special tools for everybody.

Maybe the issue resolves when the sassc provides useable artifacts for windows 
- The issue that Charles Oliver Nutter is working on (or did he gave up).

For now it looks like jekyll has 2 versions and they have both "same features", 
they differ mostly only in the change of sass and some other tools: The 4.x 
version uses sassc, while 3.x uses ruby-sass. On the other hand: do we use 
"sass" at all? If not, mabye let's exclude the dependency? SASS is for 
processing CSS templates, do we use that when building the refguide?

bq. Jekyll doesn't officially support Windows, but has some documentation on 
it: https://jekyllrb.com/docs/installation/windows/

That's about ruby itsself. The cool thing in Gradle is that we use jruby which 
has no dependencies outside the Java VM and is easier to setup. But jruby only 
works fine with pure "ruby gems", if you have native depenedencies it breaks.

> Refguide no longer builds on Windows
> ------------------------------------
>
>                 Key: SOLR-15520
>                 URL: https://issues.apache.org/jira/browse/SOLR-15520
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: main (9.0)
>         Environment: Windows 10
>            Reporter: Uwe Schindler
>            Priority: Blocker
>             Fix For: main (9.0)
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When running the gradlew build on windows, there are 2 bugs: 
> a) when it installs "sassc-2.4.0", it seems to try to compile something, 
> which won't work on windows, because you won't have a compile available. 
> Neither "make":
> {noformat}
> > Task :solr:solr-ref-guide:jrubyPrepare
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by com.headius.backport9.modules.Modules 
> (file:/C:/Users/jenkins/.gradle/caches/modules-2/files-2.1/org.jruby/jruby-complete/9.2.9.0/8e44ce7a1417966d89957bd766a148601e28828b/jruby-complete-9.2.9.0.jar)
>  to method sun.nio.ch.NativeThread.signal(long)
> WARNING: Please consider reporting this to the maintainers of 
> com.headius.backport9.modules.Modules
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Successfully installed rb-fsevent-0.11.0
> Successfully installed ffi-1.15.3-java
> Successfully installed rb-inotify-0.10.1
> Successfully installed unicode-display_width-1.7.0
> Successfully installed forwardable-extended-2.6.0
> Successfully installed rexml-3.2.5
> Successfully installed listen-3.5.1
> Building native extensions. This could take a while...
> ERROR:  Error installing 
> C:\Users\jenkins\.gradle\caches\modules-2\files-2.1\rubygems\sassc\2.4.0\3032f0c1662efc8aa04636e99a6bdefd15549fc8\sassc-2.4.0.gem:
>       ERROR: Failed to build gem native extension.
>     current directory: 
> C:/Users/jenkins/workspace/Solr-main-Windows/solr/solr-ref-guide/build/.gems/gems/sassc-2.4.0/ext
> java -cp 
> ;C:\Users\jenkins\.gradle\caches\modules-2\files-2.1\org.jruby\jruby-complete\9.2.9.0\8e44ce7a1417966d89957bd766a148601e28828b\jruby-complete-9.2.9.0.jar
>  org.jruby.Main -r ./siteconf20210706-5988-13j4z41.rb extconf.rb
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by com.headius.backport9.modules.Modules 
> (file:/C:/Users/jenkins/.gradle/caches/modules-2/files-2.1/org.jruby/jruby-complete/9.2.9.0/8e44ce7a1417966d89957bd766a148601e28828b/jruby-complete-9.2.9.0.jar)
>  to method sun.nio.ch.NativeThread.signal(long)
> WARNING: Please consider reporting this to the maintainers of 
> com.headius.backport9.modules.Modules
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> creating Makefile
> current directory: 
> C:/Users/jenkins/workspace/Solr-main-Windows/solr/solr-ref-guide/build/.gems/gems/sassc-2.4.0/ext
> make "DESTDIR=" clean
> 'make' is not recognized as an internal or external command,
> operable program or batch file.
> current directory: 
> C:/Users/jenkins/workspace/Solr-main-Windows/solr/solr-ref-guide/build/.gems/gems/sassc-2.4.0/ext
> make "DESTDIR="
> 'make' is not recognized as an internal or external command,
> operable program or batch file.
> make failed, exit code 1
> {noformat}
> b) if you have whitespace in your working dircetory path, it fails like this:
> {noformat}
> > Task :solr:solr-ref-guide:jrubyPrepare
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by com.headius.backport9.modules.Modules 
> (file:/C:/Users/Uwe%20Schindler/.gradle/caches/modules-2/files-2.1/org.jruby/jruby-complete/9.2.9.0/8e44ce7a1417966d89957bd766a148601e28828b/jruby-complete-9.2.9.0.jar)
>  to method sun.nio.ch.NativeThread.signal(long)
> WARNING: Please consider reporting this to the maintainers of 
> com.headius.backport9.modules.Modules
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Successfully installed rb-fsevent-0.11.0
> Successfully installed ffi-1.15.3-java
> Successfully installed rb-inotify-0.10.1
> Successfully installed unicode-display_width-1.7.0
> Successfully installed forwardable-extended-2.6.0
> Successfully installed rexml-3.2.5
> Successfully installed listen-3.5.1
> Building native extensions. This could take a while...
> ERROR:  Error installing C:\Users\Uwe 
> Schindler\.gradle\caches\modules-2\files-2.1\rubygems\sassc\2.4.0\3032f0c1662efc8aa04636e99a6bdefd15549fc8\sassc-2.4.0.gem:
>         ERROR: Failed to build gem native extension.
>     current directory: C:/Users/Uwe 
> Schindler/Projects/lucene/solr/solr/solr-ref-guide/build/.gems/gems/sassc-2.4.0/ext
> java -cp ;C:\Users\Uwe 
> Schindler\.gradle\caches\modules-2\files-2.1\org.jruby\jruby-complete\9.2.9.0\8e44ce7a1417966d89957bd766a148601e28828b\jruby-complete-9.2.9.0.jar
>  org.jruby.Main -r ./siteconf20210706-24280-7dgu7s.rb extconf.rb
> Fehler: Hauptklasse 
> Schindler\.gradle\caches\modules-2\files-2.1\org.jruby\jruby-complete\9.2.9.0\8e44ce7a1417966d89957bd766a148601e28828b\jruby-complete-9.2.9.0.jar
>  konnte nicht gefunden oder geladen werden
> Ursache: java.lang.ClassNotFoundException: 
> Schindler\.gradle\caches\modules-2\files-2.1\org.jruby\jruby-complete\9.2.9.0\8e44ce7a1417966d89957bd766a148601e28828b\jruby-complete-9.2.9.0.jar
> extconf failed, exit code 1
> Gem files will remain installed in C:/Users/Uwe 
> Schindler/Projects/lucene/solr/solr/solr-ref-guide/build/.gems/gems/sassc-2.4.0
>  for inspection.
> Results logged to C:/Users/Uwe 
> Schindler/Projects/lucene/solr/solr/solr-ref-guide/build/.gems/extensions/universal-java-11/2.5.0/sassc-2.4.0/gem_make.out
> {noformat}
> I set this as blocker, because it make Solr's build completely fail to do 
> precommit on my machine!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to