<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Bill,<div class=""><br class=""></div><div class="">It looks like you may have some conflicting packages installed in your anaconda environment; in particular, the fact that ncl, poppler, and poppler-data all come from the “conda-forge” channel, but fontconfig does not raises a red flag for me.</div><div class=""><br class=""></div><div class="">When using “anaconda” (as opposed to “miniconda”), the base/“root” environment contains a large collection of packages by default, which can cause conflicts with “conda-forge” packages. If you need to ensure your base environment works as is for other projects, I would instead create a new environment specifically for NCL:</div><div class=""><br class=""></div><div class=""><font face="Menlo" class="">conda create -n ncl_env -c conda-forge ncl</font></div><div class=""><font face="Menlo" class="">conda activate ncl_env<span class="Apple-tab-span" style="white-space:pre"> </span># older versions of conda use “source activate ncl_env”</font></div><div class=""><br class=""><div>While this does add an extra “activate” step before you can use NCL, it does help prevent random library incompatibility issues like what you’ve seen with fontconfig.</div><div><br class=""></div><div>If you are not as concerned about your base environment remaining in its current state, you could also just run:</div><div><br class=""></div><div><font face="Menlo" class="">conda update --all -c conda-forge</font></div><div><br class=""></div><div>This will update all of the packages in your base environment to the “conda-forge” channel version, which should allow all of the packages to work together. Note that it is possible that large version jumps can occur for some packages if you do this, so you may need to verify that everything is still backwards compatible.</div><div><br class=""></div><div>I hope this helps,</div><div>Kevin</div><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 19, 2019, at 9:17 PM, Capehart, William J via ncl-install <<a href="mailto:ncl-install@ucar.edu" class="">ncl-install@ucar.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""> Hi All.<br class=""><br class=""> Starting to see if I’m ready to try again to migrate to conda as a mac package manager due to problems with getting pyNIO/NGL working with a homebrew system.<br class=""><br class=""> Out of the gate I have the following error getting NCL installed. <br class=""><br class=""> [:~/anaconda3/lib]% ncl<br class=""> dyld: Library not loaded: @rpath/libfontconfig.1.dylib<br class=""> Referenced from: /Users/wjc/anaconda3/lib/libpoppler.78.dylib<br class=""> Reason: Incompatible library version: libpoppler.78.dylib requires version 14.0.0 or later, but libfontconfig.1.dylib provides version 13.0.0<br class=""> Abort trap: 6<br class=""><br class=""> Specific Installed addressed above:<br class=""><br class=""> ncl 6.6.2 h813f7a2_2 conda-forge<br class=""> fontconfig 2.13.0 h5d5b041_1 <br class=""> poppler 0.67.0 hf4bf5f7_1002 conda-forge<br class=""> poppler-data 0.4.9 1 conda-forge<br class=""><br class=""> Ideas appreciated.... <br class=""> Bill Capehart<br class=""><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=""></div></div></blockquote></div><br class=""></div></body></html>