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
This configuration runs make targets all (explicit) and libs (coming from self.make_args()), which both try to run openblas tests from test/ and utest/ directories compiled for a foreign architecture on a host machine:
Which causes errors, because the resulting test executable cannot be ran on a host arch.
It also passes unrelated env vars - whether you cross-compiling or not, while preventing users from setting TARGET for example.
Instead, only the make target shared (confusingly named) needs to run. Users should be in control of which env vars they want to set during cross-compilation, there is no point to pick and rename the vars in this crate - it only brings confusion and bugs.
This issue makes it impossible to cross-compile the library (combined with other defects), and therefore it makes it impossible to use math libraries which rely on this crate in a production environment.
The text was updated successfully, but these errors were encountered:
This configuration runs make targets
all
(explicit) andlibs
(coming fromself.make_args()
), which both try to run openblas tests fromtest/
andutest/
directories compiled for a foreign architecture on a host machine:openblas-src/openblas-build/src/build.rs
Lines 493 to 495 in e1fd795
Which causes errors, because the resulting test executable cannot be ran on a host arch.
It also passes unrelated env vars - whether you cross-compiling or not, while preventing users from setting
TARGET
for example.Instead, only the make target
shared
(confusingly named) needs to run. Users should be in control of which env vars they want to set during cross-compilation, there is no point to pick and rename the vars in this crate - it only brings confusion and bugs.This issue makes it impossible to cross-compile the library (combined with other defects), and therefore it makes it impossible to use math libraries which rely on this crate in a production environment.
The text was updated successfully, but these errors were encountered: