<div dir="ltr"><div><div>Please, <br><br></div>remove me from the distribution list.<br><br></div>regards<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 16, 2016 at 4:30 PM, Kevin Hallock <span dir="ltr"><<a href="mailto:hallock@ucar.edu" target="_blank">hallock@ucar.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Some of those variables <i>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><br></div><div>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><br></div><div>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><br></div><div>Thanks for the information,</div><div>Kevin<br><div><br></div><div><br><div><blockquote type="cite"><div>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" target="_blank">kevin.havener@us.af.mil</a>> wrote:</div><br><div>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><br>NCARG_FONTCAPS<br>NCARG_GRAPHCAPS<br>NCARG_DATABASE<br>NCARG_LIB<br>NCARG_NCARG<br><br>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><br>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><br>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>F951: Internal compiler error: Illegal instruction.<br>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><br>Kevin Havener<br><br>-----Original Message-----<br>From: <a href="mailto:ncl-install-bounces@ucar.edu" target="_blank">ncl-install-bounces@ucar.edu</a> [<a href="mailto:ncl-install-bounces@ucar.edu" target="_blank">mailto:ncl-install-bounces@ucar.edu</a>] On Behalf Of HAVENER, KEVIN F GS-12 USAF ACC 14 WS/WXED<br>Sent: Wednesday, March 16, 2016 12:12 PM<br>To: <a href="mailto:ncl-install@ucar.edu" target="_blank">ncl-install@ucar.edu</a><br>Subject: [ncl-install] Conda Install Report<br><br>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><br>Was surprised to see conda-ncl install a Python3 environment. Good job.<br>Tried to run the example suite as a test:<br> ncl -V: r16433 ;;expected<br> ng4ex gsun01n: resource </usr/share/ncarg/resfile> does not exist ;;unexpected<br><br>Shouldn't the test/example suite run? I did check to make sure that I was running the right ncl.<br><br>As an aside:<br><br>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><br><br>Kevin Havener<br><br>_______________________________________________<br>ncl-install mailing list<br>List instructions, subscriber options, unsubscribe:<br><a href="http://mailman.ucar.edu/mailman/listinfo/ncl-install" target="_blank">http://mailman.ucar.edu/mailman/listinfo/ncl-install</a><br>_______________________________________________<br>ncl-install mailing list<br>List instructions, subscriber options, unsubscribe:<br><a href="http://mailman.ucar.edu/mailman/listinfo/ncl-install" target="_blank">http://mailman.ucar.edu/mailman/listinfo/ncl-install</a><br></div></blockquote></div><br></div></div></div><br>_______________________________________________<br>
ncl-install mailing list<br>
List instructions, subscriber options, unsubscribe:<br>
<a href="http://mailman.ucar.edu/mailman/listinfo/ncl-install" rel="noreferrer" target="_blank">http://mailman.ucar.edu/mailman/listinfo/ncl-install</a><br>
<br></blockquote></div><br></div>