This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Thank you for your query to the ldm support system. The latest noaaport code has C++ v11 hooks that require the system that is building the code to have a C++11 compiler. I will need to get with the senior LDM developer here on the work-around, as I believe I have heard there is one. But that is the issue . . . the build is expecting a C++11 compiler, and it is not finding one on your system. >> in reply to >> I am trying to compile the LDM using the usual command ./configure --with-noaaport And when I do, this happens: make[2]: Entering directory `/home/ldm/ldm-6.13.17/src/noaaport' depbase=`echo CircFrameBuf.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\ g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../grib2 -I../gempak -I../zlib -I../log -I../log -I../protocol -I../protocol -I../protocol2 -I../protocol2 -I../registry -I../registry -I../protocol -I../pq -I../misc -I./retrans -I/usr/include/libxml2 -std=c++11 -g -O2 -MT CircFrameBuf.o -MD -MP -MF $depbase.Tpo -c -o CircFrameBuf.o CircFrameBuf.cpp &&\ mv -f $depbase.Tpo $depbase.Po cc1plus: error: unrecognized command line option "-std=c++11" make[2]: *** [CircFrameBuf.o] Error 1 make[2]: Leaving directory `/home/ldm/ldm-6.13.17/src/noaaport' make[1]: *** [install] Error 2 make[1]: Leaving directory `/home/ldm/ldm-6.13.17/src/noaaport' make: *** [install-recursive] Error 1 [ldm@machineiamon src]$ Do you have any idea what might be wrong? Ticket Details =================== Ticket ID: OYI-925913 Department: Support LDM Priority: Normal Status: Open =================== 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.