Hi Agnieszka, > I've got from a collegue your reply to the same problem, > which you provided on the 26th of JUne to Michael Schick. > It was numbered then [netCDF #PSA-339289] > > I'll study the reply and think how to work around the thing on Solaris OS v.9. > What kind of errors in the library do you believe I'll get when > I just ignore (comment out) the conflicting definitions in pstdint.h? I'm not sure, but your question reminded me to send email to the user who asked the original question, to see if he or she had come up with a workaround to the problem other than upgrading their Solaris OS or Sun Studio compiler. If I get a useful reply, I'll pass it on to you. --Russ > -----Original Message----- > From: Unidata netCDF Support [mailto:address@hidden > Sent: Thursday, July 16, 2015 6:42 PM > To: Agnieszka Troelsen > Subject: [netCDF #ZSQ-904579]: make install > > > Agnieszka Troelsen, > > Your Ticket has been received, and a Unidata staff member will review it and > reply accordingly. Listed below are details of this new Ticket. Please make > sure the Ticket ID remains in the Subject: line on all correspondence related > to this Ticket. > > Ticket ID: ZSQ-904579 > Subject: make install > Department: Support netCDF > Priority: Normal > Status: Open > > > > The NetCDF libraries are developed at the Unidata Program Center, in Boulder, > Colorado, funded primarily by the National Science Foundation. > > All support requests are handled by the development team. No dedicated > support staff are funded at this time. For this reason we cannot guarantee > response times, nor that we can resolve every support issue, although we do > our best to respond within 72 hours. > > It is in the nature of support requests that the same question is asked many > times. We urge you to search the support archives for material relating to > your support request: > > http://www.unidata.ucar.edu/search.jsp?support&netcdf > > If you are having trouble building netCDF, please take a look at the > "Building NetCDF" page: > > http://www.unidata.ucar.edu/software/netcdf/docs/building.html > > or the (unfortunately somewhat out-of-date) NetCDF Build Troubleshooter page: > > http://www.unidata.ucar.edu/software/netcdf/docs/troubleshoot.html > > Windows users should see the FAQ list: > > http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#windows_netcdf4_2 > > Complete documentation (including a tutorial, and sample programs in C, > Fortran, Java, and other programming languages) can be found on the netCDF > Documentation page: > > http://www.unidata.ucar.edu/software/netcdf/docs/ > http://www.unidata.ucar.edu/software/netcdf/examples/programs/ > > If you resolve your issue through one of these methods, please send a reply > to this email, letting us know that you no longer need support. This will > help us spend more time on netCDF development. > > Best regards, > > Unidata User Support > > > Any email message from EUMETSAT is sent in good faith but shall neither be > binding nor construed as constituting a commitment by EUMETSAT, except where > provided for in a written agreement or contract or if explicitly stated in > the email. Please note that any views or opinions presented in this email are > solely those of the sender and do not necessarily represent those of > EUMETSAT. This message and any attachments are intended for the sole use of > the addressee(s) and may contain confidential and privileged information. Any > unauthorised use, disclosure, dissemination or distribution (in whole or in > part) of its contents is not permitted. If you received this message in > error, please notify the sender and delete it from your system. > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: ZSQ-904579 Department: Support netCDF Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.