<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Some of those variables <i class="">do</i> take precedence over $NCARG_ROOT. Those variables serve a purpose in this case because the Red Hat package maintainers choose to separate files provided by NCL into different paths (/usr/lib64/ncarg, /usr/share/ncarg, …) rather than keeping everything in a single directory (“$CONDA_ENV_PATH/lib/ncarg" in our case). As such, I do not believe this to be a bug in the Red Hat ncl-6.3.0 package, but rather an incomplete configuration of environment variables within the conda environment which should ideally be set automatically.<div class=""><br class=""></div><div class="">Currently, only $NCARG_ROOT is set by the script $CONDA_ENV_PATH/etc/conda/activate.d/ncl-activate.sh, which is sourced as part of the “source activate ${env_name}” process. I will update the ncl-activate.sh and ncl-deactivate.sh scripts to set and unset the additional variables you mentioned in order to avoid conflicts like what you have experienced. This should allow for a seamless transition between your existing NCL runtime environment and your new Anaconda NCL environment without having to worry about environment variables.</div><div class=""><br class=""></div><div class="">Please note that this will only help users who are able to run “source activate ${env_name}” (bash/sh/zsh only; csh/tcsh/ksh users will have to manually manage their environment variables).</div><div class=""><br class=""></div><div class="">Thanks for the information,</div><div class="">Kevin<br class=""><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 16, 2016, at 12:29 PM, HAVENER, KEVIN F GS-12 USAF ACC 14 WS/WXED <<a href="mailto:kevin.havener@us.af.mil" class="">kevin.havener@us.af.mil</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">I think I've figured out the problem with the conda install of ncl. I am using Fedora 23. The ncl-6.3.0 package for that platform available from the Redhat repository sets several NCAR_* environmental variables. Those confused the conda install by installing additional paths beside NCARG_ROOT, which the conda install/source activate did manage to change. In addition to NCARG_ROOT, the Fedora package sets:<br class=""><br class="">NCARG_FONTCAPS<br class="">NCARG_GRAPHCAPS<br class="">NCARG_DATABASE<br class="">NCARG_LIB<br class="">NCARG_NCARG<br class=""><br class="">And I think NCARG_LIB and NCARG_NCARG conflicted with the conda install. What NCARG environment variables should be set by the Fedora package? Just NCARG_ROOT, right. The others are from long, long ago, right?<br class=""><br class="">If anyone else is following this, you have to uninstall the Fedora ncl package, and reboot. I could not locate where the rpm package sets the ncl environment variables. Or you can unset them for a single session. If anyone can clear up for me what the environment variables should be, I will file a bug report against the Red Hat package. They need to change their recipe.<br class=""><br class="">After fixing this, the examples ran correctly. Now should I expect NCAR Graphics to work, because it didn't? It failed to build the cpex08.f file with:<br class="">F951: Internal compiler error: Illegal instruction.<br class="">According to "which gcc", it tried to use the 4.8.5 from the conda ncl_test environment and not the newer system gcc.<br class=""><br class="">Kevin Havener<br class=""><br class="">-----Original Message-----<br class="">From: <a href="mailto:ncl-install-bounces@ucar.edu" class="">ncl-install-bounces@ucar.edu</a> [<a href="mailto:ncl-install-bounces@ucar.edu" class="">mailto:ncl-install-bounces@ucar.edu</a>] On Behalf Of HAVENER, KEVIN F GS-12 USAF ACC 14 WS/WXED<br class="">Sent: Wednesday, March 16, 2016 12:12 PM<br class="">To: <a href="mailto:ncl-install@ucar.edu" class="">ncl-install@ucar.edu</a><br class="">Subject: [ncl-install] Conda Install Report<br class=""><br class="">I created an environment and installed ncl under my personal conda python 2.7.10 environment. Install went fine as far as I can tell.<br class=""><br class="">Was surprised to see conda-ncl install a Python3 environment. Good job.<br class="">Tried to run the example suite as a test:<br class=""> ncl -V: r16433 ;;expected<br class=""> ng4ex gsun01n: resource </usr/share/ncarg/resfile> does not exist ;;unexpected<br class=""><br class="">Shouldn't the test/example suite run? I did check to make sure that I was running the right ncl.<br class=""><br class="">As an aside:<br class=""><br class="">Same issue with pyngl/pynio. Install went well. Examples didn't run with "libjpeg.so.8 not found" during VD_create vdatas . Here I tried to run the examples by using the run-all-ex.sh in the ~/anaconda2/envs/pyngl_test/share directory. Seems like the pynglex script on the website is outdated/not included?<br class=""><br class=""><br class="">Kevin Havener<br class=""><br class="">_______________________________________________<br class="">ncl-install mailing list<br class="">List instructions, subscriber options, unsubscribe:<br class=""><a href="http://mailman.ucar.edu/mailman/listinfo/ncl-install" class="">http://mailman.ucar.edu/mailman/listinfo/ncl-install</a><br class="">_______________________________________________<br class="">ncl-install mailing list<br class="">List instructions, subscriber options, unsubscribe:<br class="">http://mailman.ucar.edu/mailman/listinfo/ncl-install<br class=""></div></blockquote></div><br class=""></div></div></body></html>