X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 22 Dec 2012 10:29 AM by  anon
Attempt to call undefined procedure: 'CALL_EXTERNAL'
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
22 Dec 2012 10:29 AM
    Hello everyone. It appears that my installation is somehow messed up, because for some reason it isn't finding the built-in function CALL_EXTERNAL. Could someone help me figure what's going on? I'm using IDL 8.2.1, licensed to the University of Alberta. I also have the newest version of ENVI, but I'm not using it at the moment. Also, I chose default options in the installer (on LinuxMint 14.1), with the install directory as "/usr/local/exelis/". The code making the external call (to a C dynamic library) is below:
    call_external, "/home/mike/NetBeansProjects/libSPA/dist/Debug/GNU-Linux-x86/liblibSPA.so", 'vertex_extraction', data, data_info.ns, data_info.nl, $
    
        n_elements(data_info.selected_bands), data_info.number_value, data_info.sp_number, data_info.angle, $
    
        data_info.sp_a, /CDECL, /AUTO_GLUE 

    Deleted User



    New Member


    Posts:
    New Member


    --
    31 Dec 2012 01:50 PM
    Perhaps your IDL_DLM_PATH or IDL_PATH preference is messed up. For example, you might have an environment variable called IDL_DLM_PATH pointing to your dll. If this environment variable does not include the the tag, it could cause problems. I would recommend setting the IDL_PATH and IDL_DLM_PATH environment variables to , and then try restarting IDL to see if that helps with the problem. Bash: export IDL_PATH= CSH: setenv IDL_PATH

    Deleted User



    New Member


    Posts:
    New Member


    --
    31 Dec 2012 02:01 PM
    Okay, I will check that just to be sure, but just for anyone else who reads this later, I tried using the function call syntax (i.e. result = CALL_EXTERNAL(..., ..., ...)), and it worked. Thanks for getting back to me, though.

    Deleted User



    New Member


    Posts:
    New Member


    --
    31 Dec 2012 02:23 PM
    Never mind my post. The error was caused by the syntax. My apologies for steering you in the wrong direction.
    You are not authorized to post a reply.