Re: 1.0 release problems and TVM

I fixed the jar issue, also synced offline with Chris on slack Tianqi On Tue, Nov 28, 2017 at 4:55 PM, Chris Olivier wrote: > It is mentioned in the -1 email we got for rc0 release: > > Hi, > > -1 binding due to license, header issues and having a compiled jar in a >

Re: 1.0 release problems and TVM

It is mentioned in the -1 email we got for rc0 release: Hi, -1 binding due to license, header issues and having a compiled jar in a source release. I checked: - incubating in name - signatures and hashes correct - DISCLAIMER exists - LICENSE has issues (see below) I also note that license

Re: 1.0 release problems and TVM

OK, let me clarify this. NNVM now contains two part of the library, to facilitate the migration. - NNVM core library, which does not depend on tvm, and is what MXNet using now. - NNVM compiler, which depends on core library and tvm. So to build MXNet binary, you can simply use the current source

Re: 1.0 release problems and TVM

MXNet-1.0 depends on nnvm @ 8d79cfd which has TVM related commits. So one of the solution could be to go back in nnvm which doesn't include TVM. On Tue, Nov 28, 2017 at 4:41 PM, Tianqi Chen

Re: 1.0 release problems and TVM

I mean Mxnet is not using tvm as a direct dependency. The support is being done in nnvm compiler, which is not part of the release Tianqi On Tue, Nov 28, 2017 at 4:39 PM Tianqi Chen wrote: > As far as i know Mxnet is not using tvm for now. So you can simply not > ship