Thursday, December 08, 2011
Missing environment.mk and other files in SFK
Q: I have installed the BSP for SFK for 5.5.1 on my Linux system, but without installing any of the BSP documentation (I didn't need it and already have a copy of it elsewhere). When I try to build the rtose, I get a "No such file or directory" errors on rtose_defaults.mk and environment.mk.Checking the SFK delivery shows these and other important build files missing - in fact, the /refsys directory only has /rtose in it, and nothing else.
A: There is a weird problem with the installer that causes it to omit a lot of important files if you don't install the BSP documentation. Re-install it with all the documentation checked, which is the default. Then the environment.mk and other files should appear in the distro where they belong.
A: There is a weird problem with the installer that causes it to omit a lot of important files if you don't install the BSP documentation. Re-install it with all the documentation checked, which is the default. Then the environment.mk and other files should appear in the distro where they belong.
Labels: BSP, installation, OSE5, sfk
Monday, December 05, 2011
Optima error: "Unsupported color depth"
Q: I was trying to start the System Profiler feature in the Optima environment, and got an error about "Unsupported color depth" instead of the functionality I needed. What causes this and how can I get around it?
A: The underlying cause isn't clear, but typically it's seen when trying to access Optima running on a server through a remote windowing client such as Citrix, X or NX. The error is seen when trying to open the CPU Profiler or System Profiler and has been seen on both Linux and Solaris servers and with all types of client hosts. There isn't a fix for it, other than perhaps trying a different remote client type. The error is never seen when accessing Optima on the local server, and that's really the only use fully supported.
A: The underlying cause isn't clear, but typically it's seen when trying to access Optima running on a server through a remote windowing client such as Citrix, X or NX. The error is seen when trying to open the CPU Profiler or System Profiler and has been seen on both Linux and Solaris servers and with all types of client hosts. There isn't a fix for it, other than perhaps trying a different remote client type. The error is never seen when accessing Optima on the local server, and that's really the only use fully supported.
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.)
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: installation, OSE, refsys, windows 7
free invisible web counter
