Jenn's Support Shop

Problem: OSEck 3.1 and Illuminator require different license files

Symptom:
One of the products displays "unable to get license" error on launch, because LM_LICENSE_FILE and/or the Illuminator configuration are pointing to an incorrect file.

Solution:
Set environment variable LM_LICENSE_FILE to point to the license.dat for OSEck. Then start Illuminator. Enter "File" menu and select "Preferences", followed by "License" tab. Set the license to point to the Illuminator license.dat . They can be different files in different places.
------------------------------------------------------
Problem: Soft Kernel compiling for 5.1 : cannot use ARCH=sfk-win32

Symptom:
make lm ARCH=sfk-win32
Error: module X does not build as a load module

Solution:
The soft kernel compile for refsys in 5.1 cannot use ARCH as
sfk-win32 or any other sfk designation. Need to use x86, solaris or similar.
See: $OSE_ROOT/refsys/modules/modules.mk for rules used by make
to determine.
--------------------------------------------------------
Problem: unable to get license for Illum. 1.1 tools release

Symptom:
Fire up Tools 1.1 Illum. and get "could not get the license" error window.

Solution:
The Illuminator release for Tools 1.1 (shipped apart from 5.1)
requires the tools flexlm license.dat rather than the one for 5.1 soft kernel.
Use the tools 1.1 license to get Illuminator functionality for this release.
--------------------------------------------
Problem: Unable to compile on 4.4.1 using gcc

Symptom: varies but usually see output like:
C:\OSE\common\src\startefs
.c /cygdrive/c/DOCUME~1/NSHEVC~1/LOCALS~1/Temp/cc4eHC5U.i
powerpc-eabi-gcc: Internal compiler error: program cpp got fatal signal
11
dmake.exe: Error code 129, while making '..\obj\\startefs.o'

Solution:
Add to your root /cygwin.bat for OSE 4.4.1 the following define:
GCC_EXEC_PREFIX=/cygdrive/c/OSE/OSE4.4.1/win32/lib/gcc-lib/
--------------------------------