aGiant opened a new issue #5709:
URL: https://github.com/apache/incubator-tvm/issues/5709


   
   - Ubuntu 18.04 LTS
   - LLVM installed according to https://apt.llvm.org/
   - tvm was successfully compiled and worked well using python 3.7 with MXNet.
   - tvm 0.7 dev
   
   But for this example under tvm/apps/bundle_deploy/build, dynamic and static 
libs, described in offical web site, did not work at all. Tried many times but 
always the same error: 
   
   In file included from runtime.c:61:0:
   ../../src/runtime/crt/crt_backend_api.c: In function 
‘TVMBackendRegisterSystemLibSymbol’:
   ../../src/runtime/crt/crt_backend_api.c:49:3: error: ‘g_fexecs’ undeclared 
(first use in this function)
      g_fexecs = vrealloc(g_fexecs, sizeof(TVMPackedFunc) * (g_fexecs_count + 
1));
      ^~~~~~~~
   ../../src/runtime/crt/crt_backend_api.c:49:3: note: each undeclared 
identifier is reported only once for each function it appears in
   ../../src/runtime/crt/crt_backend_api.c:49:40: error: ‘TVMPackedFunc’ 
undeclared (first use in this function); did you mean ‘TVMPackedCFunc’?
      g_fexecs = vrealloc(g_fexecs, sizeof(TVMPackedFunc) * (g_fexecs_count + 
1));
                                           ^~~~~~~~~~~~~
                                           TVMPackedCFunc
   ../../src/runtime/crt/crt_backend_api.c:49:58: error: ‘g_fexecs_count’ 
undeclared (first use in this function); did you mean ‘g_fexecs’?
      g_fexecs = vrealloc(g_fexecs, sizeof(TVMPackedFunc) * (g_fexecs_count + 
1));
                                                             ^~~~~~~~~~~~~~
                                                             g_fexecs
   Makefile:87: recipe for target 'build/bundle_c.so' failed
   make: *** [build/bundle_c.so] Error 1


----------------------------------------------------------------
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]


Reply via email to