• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 101 subscribers
  • Views 3512 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

xs.x86U: error: can't create session manager: can't find JVM

Helmut Forren
Mastermind 6805 points

I'm totally confused.  I had a working make environment.  I've been working on integrating it with svn.  Now, all of a sudden, I get the error message when I try to make my application: 

.../dvsdk/dvsdk_3_10_00_11/xdctools_3_16_01_27/xs.x86U: error: can't create session manager: can't find JVM

The dvsdk folder name is preceeded by more stuff to get to that level.  This stuff shouldn't be germane, so I've left it out.

When I google for this error, I either can't find anything or find far too much to cull out what I need.  

I didn't intentionally do anything to a JVM.  I don't know exactly what xs.x86U does.  I tried rebooting.

Did I blow up an environmental variable?  What did I possibly do?  The only thing I know to do is to try to find the JVM and pointers (env vars) to it, but I can't figure out how to even get to first base on that task.

Please help!!!   In fact, if you have both time and inclination, you can call me a 770 three four five 7634, US EST 6am-10pm, and guide me by the hand!

  • 0
    Mastermind 6805 points

    I have a temporary workaround.  It seems .../dvsdk/dvsdk_3_10_00_11/xdctools_3_16_01_27/jre got corruped by putting it into svn, deleting it, and then checking it out again.  I'm trying to include in svn the whole dvsdk, which I've had to customize.  I have no clue what ...

    Ah, maybe here's the problem.  I needed to "make dvsdk" before "make apps", because a clean had happened before, which must have cleaned out the executable from jre, that's needed for "make apps".  I don't have the prior bad environment anymore to make sure, but I'll assume that must be my problem.

  • 0 in reply to Helmut Forren
    Prodigy 10 points

    We had this same problem-- built fine directly from the dvr_rdk, but after checking out a fresh svn copy, make sys_all would throw the following error:

    # Making syslink-rtos in ti/syslink
    making .libraries: Thu Aug 8 10:50:44 EDT 2013 ...
    ======== .interfaces [/home/xxxxx/tdvr-3.5/ti_tools/syslink/syslink_2_20_02_20/packages/ti/syslink] ========
    making package.mak (because of package.bld) ...
    /home/xxxxx/tdvr-3.5/ti_tools/xdc/xdctools_3_23_03_53/xs.x86U: error: can't create session manager: can't find JVM
    making package.mak (because of package.bld) ...
    /home/xxxxx/tdvr-3.5/ti_tools/xdc/xdctools_3_23_03_53/xs.x86U: error: can't create session manager: can't find JVM
    gmake[1]: *** No rule to make target `package.mak', needed by `.interfaces'. Stop.
    gmake: *** [/home/xxxxx/tdvr-3.5/ti_tools/syslink/syslink_2_20_02_20/packages/ti/syslink,.interfaces] Error 2
    make[4]: *** [syslink-rtos] Error 2
    make[3]: *** [syslink-rtos] Error 2
    make[2]: *** [syslink_build] Error 2
    make[1]: *** [syslink_rtos] Error 2
    make: *** [syslink] Error 2

    As it turns out, our svn import tagged all the shared library .so objects in ../jre/lib/i386 as 'svn-ignore'.  So pulling a fresh update from svn had omitted those libs.