zachgk opened a new pull request #13364: [MXNET-1225] Always use config.mk in 
make install instructions
URL: https://github.com/apache/incubator-mxnet/pull/13364
 
 
   ## Description ##
   Arguments to make for the mxnet build can be passed either directly through 
the command line or through config.mk. The install instructions are 
inconsistent and use both options. However, some frontends such as scala 
require the arguments as well so they must be passed to both the initial make 
and the following "make scalapkg". Failure to pass the arguments to the 
scalapkg make can result in an improper configuration and slower performance. 
To resolve this, I am switching the install instructions to consistently use 
the config.mk because it is automatically used by all make commands which 
resolves the potential frontend problems.
   
   ## Checklist ##
   ### Essentials ###
   Please feel free to remove inapplicable items for your PR.
   - [x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to 
the relevant [JIRA issue](https://issues.apache.org/jira/projects/MXNET/issues) 
created (except PRs with tiny changes)
   - [x] Changes are complete (i.e. I finished coding on this PR)
   - [x] Code is well-documented: 
   - For user-facing API changes, API doc string has been updated. 
   - For new C++ functions in header files, their functionalities and arguments 
are documented. 
   - For new examples, README.md is added to explain the what the example does, 
the source of the dataset, expected performance on test set and reference to 
the original paper if applicable
   - Check the API doc at 
http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
   - [x] To the my best knowledge, examples are either not affected by this 
change, or have been fixed to be compatible with this change
   
   @nswamy @lanking520 @yzhliu @andrewfayres @piyushghai 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to