From 0d3fea6bb5239ba3597b316c72c3386ab4859197 Mon Sep 17 00:00:00 2001 From: Nikita Titov Date: Sat, 20 Jul 2024 16:39:46 +0300 Subject: [PATCH 1/2] fix link to multiple OpenMP issue description --- docs/FAQ.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/FAQ.rst b/docs/FAQ.rst index 4584863180d4..2363dd6c42a5 100644 --- a/docs/FAQ.rst +++ b/docs/FAQ.rst @@ -202,7 +202,7 @@ If you are using any Python package that depends on ``threadpoolctl``, you also Detailed description of conflicts between multiple OpenMP instances is provided in the `following document `__. -**Solution**: Assuming you are using LightGBM Python-package and conda as a package manager, we strongly recommend using ``conda-forge`` channel as the only source of all your Python package installations because it contains built-in patches to workaround OpenMP conflicts. Some other workarounds are listed `here `__. +**Solution**: Assuming you are using LightGBM Python-package and conda as a package manager, we strongly recommend using ``conda-forge`` channel as the only source of all your Python package installations because it contains built-in patches to workaround OpenMP conflicts. Some other workarounds are listed `here `__. If this is not your case, then you should find conflicting OpenMP library installations on your own and leave only one of them. From 2ab1aeeca2e04a0859f52c6fbdf48f57bbe293c2 Mon Sep 17 00:00:00 2001 From: Nikita Titov Date: Sat, 20 Jul 2024 17:49:48 +0300 Subject: [PATCH 2/2] remove anchor --- docs/FAQ.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/FAQ.rst b/docs/FAQ.rst index 2363dd6c42a5..3917b27a183a 100644 --- a/docs/FAQ.rst +++ b/docs/FAQ.rst @@ -202,7 +202,7 @@ If you are using any Python package that depends on ``threadpoolctl``, you also Detailed description of conflicts between multiple OpenMP instances is provided in the `following document `__. -**Solution**: Assuming you are using LightGBM Python-package and conda as a package manager, we strongly recommend using ``conda-forge`` channel as the only source of all your Python package installations because it contains built-in patches to workaround OpenMP conflicts. Some other workarounds are listed `here `__. +**Solution**: Assuming you are using LightGBM Python-package and conda as a package manager, we strongly recommend using ``conda-forge`` channel as the only source of all your Python package installations because it contains built-in patches to workaround OpenMP conflicts. Some other workarounds are listed `here `__ under the "Workarounds for Intel OpenMP and LLVM OpenMP case" section. If this is not your case, then you should find conflicting OpenMP library installations on your own and leave only one of them.