-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential issue with XQuartz version #42
Comments
Another with Quartz above 2.7.9 is launching ql2. If one starts via a "run" script like "run_sql2", the xterm it launches may disappear. If one runs the IDL command directly, you could see this error: Error: attempt to add non-widget child "dsm" to parent "idl" which supports only widgets Googling this error gives several examples of possible solutions. This one worked for me: Quoting from this source: The solution (aside from filing bug reports against Motif) is to edit the DYLD_LIBRARY_PATH ---environment variable so that it includes the directory /opt/X11/lib/flat_namespace/ In the specific case of IDL, the idl startup script (/Applications/exelis/idl/bin/idl) contains a section which amends that variable. It’s an sh script, so if your shell is bash then it should pick up your edits. However many IDL users are also SSWIDL users, and they usually have their shell set to tcsh. In that case it’s probably simplest to edit the ‘idl’ script as follows, around line 245: if [ "$DYLD_LIBRARY_PATH" = "" ]; then |
Going back to xquartz 2.7.8 will also fix this. |
Using C shell, I needed to add my idl directory (e.g. /Applications/exelis/idl/bin) directly in my path in my .cshrc file. Simply having an alias or sourcing this idl directory in my .cshrc file is not enough. |
When the most recent version of XQuartz is installed (2.7.11), the following error appears in the terminal when running run_odrp:
xterm: Can't execvp idl: No such file or directory
This happens even when the pipeline itself is installed directly. To get the pipeline to work, a separate command needs to be run in the terminal:
idl -IDL_STARTUP ${OSIRIS_BACKBONE_DIR}/drpStartup.pro ${OSIRIS_BACKBONE_DIR}/osiris_drp_backbone_startup.pro
The text was updated successfully, but these errors were encountered: