how about using two env variables: CUDA=9.0 or 10.0; DIST (set or not set) for nccl and mpich. instead of enumerating all combinations, we can only compile SINGA for the following 3 cases CUDA=9.0 CUDA=10.0 CUDA=10.0 with DIST
On Fri, Mar 13, 2020 at 10:06 PM GitBox <[email protected]> wrote: > chrishkchris edited a comment on issue #624: [WIP] SINGA-487 Include NCCL > and MPICH in conda build > URL: https://github.com/apache/singa/pull/624#issuecomment-598734929 > > > I simplified the selection logic to use only one environment variable > CUDA: > 1. export CUDA = 9.0, then use CUDA9.0 without nccl and moich > 2. export CUDA = 10.0, then use CUDA10.0 without nccl and mpich > 3. export CUDA = DIST, then use CUDA10.0 WITH nccl and mpich > 4. without export CUDA, then use CPU only > > If we need two environment variables (CUDA and DIST) to determine the > selection logic, I can change it. > > ---------------------------------------------------------------- > This is an automated message from the Apache Git Service. > To respond to the message, please log on to 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 >
