<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi Mary.<div><br></div><div>For the C compiler, I am just using MacPorts defaults. This time it turned out to be h5cc, which I think is harmlessly wrapped around Apple's clang compiler.</div><div><br></div><div>In the build log, I see that the rgb executable is run twice for no good reason. I suspect that Macports is running parallel threads, so two simultaneous rgb runs are writing on top of the same two output files, thereby corrupting both. Sure enough, when I forced a single thread build, the two database files were now written correctly.</div><div><br></div><div>Assuming this is the right answer, I will post a single thread workaround to the Macports ticket. If it is possible to force single thread within the yMakefile for rgb, that would be a good conservative improvement within the NCARG source code.</div><div><br></div><div> <a href="https://trac.macports.org/ticket/57728" target="_blank">https://trac.macports.org/ticket/57728</a></div><div><br></div><div>Thanks for your observations and suggestion to simplify the compile command. This led me to notice the parallel runs in the build log.<br></div><div><br>--Dave<br><br><br><div class="gmail_quote"><div dir="ltr">On Tue, Dec 11, 2018 at 12:47 PM Mary Haley <<a href="mailto:haley@ucar.edu">haley@ucar.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-size:small">Hi Dave,</div><div style="font-size:small"><br></div><div style="font-size:small">I don't think anybody has a clue about this one and hence the lack of a quick response. </div><div style="font-size:small"><br></div><div style="font-size:small">What version of what compiler are you using? I see references to clang and gcc3 in your output, but it's not clear.</div><div style="font-size:small"><br></div><div style="font-size:small">Sometimes when I get errors like this I try to compile the same code but with the bare minimum of possible options. For example:</div><div style="font-size:small"><br></div><div><div> cd $NCARG/ni/src/db/rgb</div><div> make clean</div><div> clang -I../../../.././include -c rgb.c</div><div><div> clang -o rgb rgb.o -L../../../.././common/src/libncarg_c -lncarg_c</div></div><div> make install</div><div><br></div><div>This should make the "rgb" executable, and then install the three rgb.xxx files to $NCARG_ROOT/lib/ncarg/database. You can then try the cn05n.ncl example again.</div><div><br></div><div>In your case, you'll want to substitute "clang" with whatever compiler you're using. </div><div><br></div><div>If this works, then I would take a closer look at the various options that are being set when you compile the code using your own options, which looks to be this:</div><div><br></div><div><div>/Users/dallured/macports/254/bin/glibtool --tag=CC --mode=compile /usr/bin/clang -DHAVE_CONFIG_H -I. -I. -I.. -I. -DUSE_INTERP_RESULT -I/Users/dallured/macports/254/include -pipe -Os -arch x86_64 -Wall -I/Users/dallured/macports/254/include -c -o rgb.lo `test -f rgb.c || echo './'`rgb.c</div><div><br></div><div>I tried a subset of these options, and it worked fine for me:</div><div><br></div><div><div>clang -c -I../../../.././include -c -pipe -Os -arch x86_64 -Wall rgb.c</div><div>clang -o rgb rgb.o -pipe -Os -arch x86_64 -Wall -L../../../.././common/src/libncarg_c -lncarg_c</div><div><br></div><div>--Mary</div><div><br></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Dec 6, 2018 at 1:51 PM Dave Allured - NOAA Affiliate via ncl-install <<a href="mailto:ncl-install@ucar.edu" target="_blank">ncl-install@ucar.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr">NCL support,</div><div dir="ltr"><br></div><div dir="ltr">I am debugging Macports builds of NCARG/NCL 6.5.0 on Mac OS 10.13.6 (High Sierra). My current build recipe works pretty well. However, there are errors in the two RGB database files that are generated during the build process. This leads to defects in output plots. This is demonstrated by some of the example programs, such as:<div><br></div><div><div><font face="monospace, monospace"> mac56:~/temp/x 31> ng4ex cn05n</font></div><div><font face="monospace, monospace"> NCAR Graphics NCL Example <cn05n></font></div><div><font face="monospace, monospace"> Copying cn05n.ncl</font></div><div><font face="monospace, monospace"> Running NCL...</font></div><div><font face="monospace, monospace"> Copyright (C) 1995-2018 - All Rights Reserved</font></div><div><font face="monospace, monospace"> University Corporation for Atmospheric Research</font></div><div><font face="monospace, monospace"> NCAR Command Language Version 6.5.0</font></div><div><font face="monospace, monospace"> The use of this software is governed by a License Agreement.</font></div><div><font face="monospace, monospace"> See <a href="http://www.ncl.ucar.edu/" target="_blank">http://www.ncl.ucar.edu/</a> for more details.</font></div><div><font face="monospace, monospace"> fatal:CvtStringToColorIndex: Unable to convert string "PaleGreen4" to requested type</font></div><div><font face="monospace, monospace"> warning:Error retrieving resource lbTitleFontColor from args - Ignoring Arg</font></div><div><font face="monospace, monospace"> fatal:CvtStringToColorIndex: Unable to convert string "PaleGreen4" to requested type</font></div><div><font face="monospace, monospace"> warning:Error retrieving resource tiMainFontColor from args - Ignoring Arg</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace"> <truncated></font></div></div><div><br></div><div>This is caused by bad files rgb.dir and rgb.pag that are generated by rgb.c when building NCARG. I can plug in correct database files from other sources, and these NCL color errors go away. The current Macports build throws several warning messages about rgb.c. There is a current Macports ticket with more details, including a build console log that shows the rgb.c warnings:</div><div><br></div><div> <a href="https://trac.macports.org/ticket/57728" target="_blank">https://trac.macports.org/ticket/57728</a></div><div><br></div><div>It is unclear to me whether the problem is in rgb.c itself, or in the Macports build environment. Either is possible. Can you please take a look and advise on a possible solution? Thanks.</div><div><br></div><div>--Dave</div></div></div></div>
</blockquote></div>
</blockquote></div></div></div></div></div></div></div>