| 11 Jun 2009 12:09 AM |
|
|
I have installed IDL 7.1 on Fedora 10, following the instructions here:
download.ittvis.com/idl_7.1/linux/web_install_idl_all.html
I then attempt to follow the licensing wizard, by running 'ittlicense' and I get the following error:
[root@localhost itt]# ittlicense
IDL Version 7.1 (linux x86_64 m64). (c) 2009, ITT Visual Information Solutions
% Embedded IDL: ITT Visual Information Solutions, License Wizard.
% Attempt to call undefined procedure/function: 'IDLRTMAIN'.
% Execution halted at: $MAIN$
I have my environment variables set up correctly (calling the 'idl_setup.bash' script from my bash profile).
'grep 'IDLRTMAIN' -r .' tells me that IDLRTMAIN is located in idl71/bin/bin.linux.x86_64/libidl.so.7.1
Has anyone else had this problem and how can I solve it?
|
|
|
|
Deleted User
New Member
Posts:  
| 11 Jun 2009 08:03 PM |
|
|
I was missing some of the 32 bit libraries.
I have since followed the steps outlined in the tech tip, to the letter, yet I am still getting the following error when I attempt to run the licence wizard:
[root@localhost bin]# ittlicense
IDL Version 7.1 (linux x86_64 m64). (c) 2009, ITT Visual Information Solutions
% Embedded IDL: ITT Visual Information Solutions, License Wizard.
% Attempt to call undefined procedure/function: 'IDLRTMAIN'.
% Execution halted at: $MAIN$
I can run idl and idlde fine (obviously they open in demo mode), just not the licence wizard - which is obviously kind of important!
|
|
|
|
Deleted User
New Member
Posts:
| 16 Dec 2010 09:04 AM |
|
|
Hi, Was there ever any solution to this issue? I'm having the same problem running ittlicense for idl 8.0 on Fedora 14 64-bit. Again, idl and idlde run fine.
Rich
|
|
|
|
Deleted User
New Member
Posts:
| 19 Jan 2011 10:40 AM |
|
|
My guess would be the IDL_PATH. Check to see if you have the IDL_PATH environment variable set (and for that matter any IDL_* related environment variables). If you do have it set, what is it set to. For example, check this:
printenv | grep IDL
If for example you have IDL_PATH set and you do not have the token included in the path, IDL will likely not be able to find many of it's components. For example:
export IDL_PATH="":/your/other/programs
This could also be set via the IDL Workbench preferences. For example if you look at the Path settings there and you do not have the IDL_DEFAULT listed, click the "insert default" button and move it to the top of the list.
-Josh
ITTVIS
|
|
|
|