Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Updates to installation instructions on Linux #256
You can find Linux installation instructions fixes on below.
With Fedora and Red Hat Linux the installation command is
If you have it installed already, then you will get acknowledgment “Nothing to do”.
Download this file: acml-5-3-1-ifort-64bit.tgz
You can combine various .bashrc changes to together as:
Follow Setup-CNTK-on-Linux except the directory name is in uppercase as it is defined in GIT:
If you have 8 GB memory or less then you must use regular compilation command “make all” instead of “make -j all”. The latter is tens of times slower as the memory amount is not sufficient for concurrent compilation. Concurrent compilation also gave me an error which I didn't get when compiling with a single process.
Run the test cases as instructed. CPU test case gives one more line than documented.
Timo, thank you for these updates. A couple of comments.
ACML. I fixed the error regarding
Installation directory. I fixed the text in a way that the CNTK folder will be always in small letters, i.e.
P.S. As you saw we describe the specific commands for Ubuntu. The reason is simple - it is the system we build and test on. I plan to review Linux setup instructions one day and update ALL sections with other popular distribution specific commands. So thank you once again.
Ah, I didn't know you can change the casing so easily with git, it works correct now.
Yes, I noticed your commands were for Ubuntu, but it is of course nice to mention if the framework is likely to work even when you don't officially support them. Fedora at least compiled and ran the basic version.
Also I would recommend to change the recommended compilation on first attempt to "make -j 3" to avoid situations like I got. My settings are "Intel® Core™ i7-4500U CPU @ 1.80GHz × 4" with 8 GB memory and without SDD drive which should be very typical for a testing and development environment. That means it has four threads, so the user is still able to kill the process if the compilation takes hours instead of minutes. This environment has too much processor capacity vs. memory + disk, which creates an outcome where each thread reads the hard drive replacing from cache something critical from other threads. So running concurrently was dozens of times slower than running on one thread only.