Avraham Adler

For the record, zlib is considered a free use license: https://en.wikipedia.org/wiki/Zlib_License https://www.gnu.org/licenses/license-list.html#ZLib http://directory.fsf.org/wiki/Zlib https://opensource.org/licenses/Zlib

I got the following just now too: ``` [12-May-2020 19:12:22 UTC] PHP Warning: preg_replace(): Compilation failed: invalid range in character class at offset 4 in ***/wp-content/plugins/crayon-syntax-highlighter/crayon_langs.class.php on line 340 ```

This project is defunct; switch to [Urvanov Syntax Highlighter](https://wordpress.org/plugins/urvanov-syntax-highlighter/) ([Github here](https://github.com/urvanov-ru/crayon-syntax-highlighter)) which is Crayon brought up to date.

This does not work either: ``` D:\LightGBM\build>cmake -A x64 -DUSE_GPU=1 -DBOOST_ROOT=C:/local/boost_1_78_0 .. -- Building for: Visual Studio 17 2022 -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19043. --...

Thank you, @jameslamb, for the quick response. What I mean by "doesn't work" is that I pass a boost root directory "C:/local/boost_1_78_0" that is not registered by the script: "found...

## Update Looking at another issue, I found that despite the script not registering -DBOOST_HOME etc, if I changed the name of `C:\local\boost_1_78_0\lib64-msvc-14.3` to `C:\local\boost_1_78_0\lib` and move the "local" subdirectories...

Thanks. That worked for registering VS 17/2022, but we're back to the parsing issue. When nothing is passed other than `--use-gpu` then despite finding the proper path when building the...

Hi, @jameslamb. Just confirming this is still an issue with 3.3.2.99 version [9489f87](https://github.com/microsoft/LightGBM/commit/9489f878b3568e70b441e5df602483e116f24cc6). Thanks

Hi @jameslamb. New version so I thought I'd check the BOOST issue. Still not working unless I am doing something wrong. Note where I **say** the libraries should be and...

I believe I am [that user](https://discuss.xgboost.ai/t/installing-xgboost-with-gpu-support-for-r-on-windows-build-does-not-complete/2227/17). I continue to have issues with VS 2022, 2019, and 2017, althouh error now is not the same as before and it is the...