-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[RESOLVED] unsupported option '-fopenmp' on Mac OS X #3
Comments
Actually, It is not tested on OSX now. Will fix soon |
Maybe it'll work with Clang updated, I'll try. |
hi, @Yorko , we currently doesn't have clear plan to support OSX (but it should have). However, this issue is caused by that OpenMP is needed by lightGBM for building, please refer to https://clang-omp.github.io/ for the instuctions |
I'll close this issue first, please feel free to reopen if the problem still there after installing OpenMP properly. |
On mac os sierra, installing OpenMPI with with homebrew and following instructions still resulted in same error. Installing using C++11 mode and with C++ MPI bindings (these were flags for the homebrew recipe) did not fix the error. |
hi @sooheon , i'm not quite sure that you are confusing openMP with openMPI(or just an typo) which doesn't needed by lightGBM by default. if you using gcc as your default compiler on sierra. the build should succeed. |
Compiling LightGBM with gcc-6 on OSX works:
|
Thank you I was indeed confusing OpenMPI and OpenMP |
@bartleusink , thanks for your sharing |
@bartleusink Thank you! If anybody's interested: I had to additionally link brew to gcc so that g++-6 is in path.
|
@Yorko Hi. I tried doing the brew link --overwrite gcc and got this error do you know why? |
Same problem as BeatricGR! Any ideas? |
@BeatriceGR @ktorimaru
|
By the way, non-Apple LLVM on macOS works just fine, as well. Just use |
Hi ! I'm trying to install gcc --without-multilib too, but the option seems to have disappeared from brew. The command given by @guolinke does'n work any more. BTW, im on High Sierra, 10.13.1. Any luck that you guys have a solution ? Thanks, |
* add init_score & test cpp and python result consistency * try fix common.h * Fix tests (#3) * update atof * fix bug * fix tests. * fix bug * fix dtypes * fix categorical feature override * fix protobuf on vs build (#1004) * [optional] support protobuf * fix windows/LightGBM.vcxproj * add doc * fix doc * fix vs support (#2) * fix vs support * fix cmake * fix #1012 * [python] add network config api (#1019) * add network * update doc * add float tolerance in bin finder. * fix a bug * update tests * add double torelance on tree model * fix tests * simplify the double comparison * fix lightsvm zero base * move double tolerance to the bin finder. * fix pylint * clean test.sh * add sklearn test * remove underline * clean codes * set random_state=None * add last line * fix doc * rename file * try fix test
@Clovel after installing |
@piotrek1543 THANK YOU! Only solution after fighting for hours. |
@Clovel |
Please have a look at : |
Can anyone solve my issue: I am totally new to terminal and want to use openmp but I am getting above error; I copied and run all the above commands (as mentioned above) but the problem persists. Currently, I am using high Sierra 10.13.6. |
@itzzmeanmol , we're testing compiler with Clang. would you give a shot of the latest instruction doc |
It generated this error: |
try with only -openmp... |
So in cmakelist we should |
After installing gcc with |
@Yassunaga it works but why does specifying the version helps lol |
@yinhaosen because calling |
Hi, I have the same problem:
If I do
so
But I need to use Fortran as well! Could you help me?? |
After trying to run with gcc-9 I'm getting the following message:
What can I do to try and run with the -fopenmp? |
Try compiling your .c file using gcc-6
The above command worked for me in my OSX-10.15.2(Catalina) machine after binging with this problem for days |
Is Mac OS X supported?
I'm on 10.12 Sierra and get the "unsupported option '-fopenmp'" error after "make -j"
The text was updated successfully, but these errors were encountered: