You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems brew installing latest libomp has dependencies that do not exist on build machines. Investigate what those dependencies are by taking a trace and install them.
wschin
added
bug
Something isn't working
P0
Priority of the issue for triage purpose: IMPORTANT, needs to be fixed right away.
labels
May 21, 2019
najeeb-kazmi
added
P1
Priority of the issue for triage purpose: Needs to be fixed soon.
and removed
P0
Priority of the issue for triage purpose: IMPORTANT, needs to be fixed right away.
labels
May 24, 2019
antoniovs1029
added
Build
Build related issue
P0
Priority of the issue for triage purpose: IMPORTANT, needs to be fixed right away.
and removed
P1
Priority of the issue for triage purpose: Needs to be fixed soon.
labels
Jan 9, 2020
We have taken a dependency on libomp version 7.0.0 rather than installing the latest version. brew install libomp will install the latest version, which we do not want as it means testing and possibly updating ML.NET to be compatible with the latest version whenever a new version is released.
In homebrew, it is possible to install a specific version brew install [email protected] only if a "tap" is maintained for that formula for the specific version. Since this "tap" is not maintained, the way to install the specific version is to point to the specific commit in the homebrew repository corresponding to the correct version. This is what we have in our CI builds.
It seems brew installing latest libomp has dependencies that do not exist on build machines. Investigate what those dependencies are by taking a trace and install them.
Related to #3694
The text was updated successfully, but these errors were encountered: