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
Some install.sh scripts are formed of two steps: first they compile the benchmark and then they run some decompressing. Take the example of git/aom-av1-1.1.0 (comments mine):
Some install.sh scripts are formed of two steps: first they compile the benchmark and then they run some decompressing. Take the example of git/aom-av1-1.1.0 (comments mine):
However the script does not fail when the compilation fails and it will run the decompressing for no good reason, wasting time and CPU cycles.
What's my use case? I'm trying to see if some test profiles respect the CC/CXX variables set in the environment before calling something as:
I set CC=CXX=/garbage and clearly the compilation step fails but then the decompressing stars and takes an annoying amount of time.
The text was updated successfully, but these errors were encountered: