Friday, January 13, 2012

 

Setting up a new windows system for java clients

Q: I am trying to run our (admittedly old...) Illuminator tool on a new Windows 7 system. I have set up Java before to run the illuminator.bat file directly, but I'm getting this generic java error:

$ ./illuminator.bat
Exception in thread "main" java.lang.NoClassDefFoundError: osedbg/launchpad/Main

Caused by: java.lang.ClassNotFoundException: osedbg.launchpad.Main
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
Could not find the main class: osedbg.launchpad.Main. Program will exit.

jemi@USPHOWS130 /cygdrive/e/OSE/OSE4.6.1/win32/bin
$ export PATH="$PATH;E:/OSE/OSE4.6.1/win32/bin"

jemi@USPHOWS130 /cygdrive/e/OSE/OSE4.6.1/win32/bin
$ echo $OSE_ROOT
C:/OSE/OSE5.5.1_PPC

jemi@USPHOWS130 /cygdrive/e/OSE/OSE4.6.1/win32/bin
$ export OSE_ROOT="E:/OSE/OSE4.6.1"


A: First off, make sure you have jre 1.6 reachable, somewhere. It should have been installed in the OSE4.6.x area but you can use your own version as well. Then make sure you have these environment variables defined before you invoke illuminator.bat:


$ export OSE_ROOT="E:/OSE/OSE4.6.1"
$ export PATH="$PATH;E:/OSE/OSE4.6.1/win32/bin"
$ export CLASSPATH=".;E:/OSE/OSE4.6.1/win32/lib"

(the CLASSPATH may or may not be necessary depending on which java you're using)

IF you set up all this, then Illuminator should finally kick off correctly.

Q: I got Illuminator up on Windows 7 finally. But now I am seeing a flexlm license error "no such license", but I know that the license file is indeed being pointed to in the correct place, where $LM_LICENSE_FILE says it is.

A: For reasons unknown, the Java client for Illuminator is looking for the user's license file in a preferences file, illuminator.prf . This is thought (at least, by Illuminator) to reside in some place like "C:/User/jemi/illuminator.prf." If you touch this file, and you'll likely have to since it doesn't actually exist yet, you can edit it to add this line:

LM_DEMO_FILE = C:/flexlm/license.dat

That will greatly aide your Illuminator to find the correct file and remove the error.

Labels: , , ,


Thursday, December 01, 2011

 

Build errors: "The syntax of the command is incorrect"

Q: I'm switching over to windows 7 and am having problems getting ose to build. I followed the instructions in the installation guide regarding installing as admin etc., but am seeing the following errors:

make all FLAVOR=debug

The syntax of the command is incorrect.
"--- Making modules/badapp"
The syntax of the command is incorrect.
"--- Compiling src/badapp.c"
"--- Making modules/corecmds"
The syntax of the command is incorrect.
"--- Compiling src/cmd_pool.c"
"--- Making modules/ddi"
I'm also seeing this problem with sigdb1:
SigDB1: Error: I/O error using file: obj\rtose_debug\sigdb1.c (The system cannot find the path specified)
make[1]: *** [obj/rtose_debug/sigdb.c] Error 1
"--- Error building RTOSE(debug) for C:\Enea\OSE\BSP_P2020RDB_OSE5.5\refsys\rtose\p2020rdb"

A: This is likely an installation issue with Windows 7.
Re-install and re-run the install using all the instructions in the OSE installation doc for changing UAC permissions etc. After about the 3rd time and several reboots it started working. (info from Larry G)

Change the owners from "admin" to yourself, i.e. your own account, reboot, rebuild. (from J.M.)

Make sure you're using cygwin, not DOS - alot of the commands no longer work with DOS. (from E.B.)
 

Labels: , , ,


This page is powered by Blogger. Isn't yours?

free web hit counter
free invisible web counter