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.
Harald, > I do not have root privileges on the machine where I am trying to compile. > Frankly, I think that one should never need superuser privileges to just > *compile* any piece of software. I sympathize with your frustration. I, too, have experienced packages that have an inconvenient attribute. On every system I've ever encountered, the file "/etc/rsyslog.conf" is world-readable by default. That it's not indicates that your system administrator favors security over productivity (unnecessarily so, in my opinion). Unfortunately, this causes the autoconf(1)-based build mechanism to terminate the configure(1) script. Logging must be enabled in order for the LDM system to work correctly. If the configure(1) script can't figure-out the logging system, then there's no sense in building the LDM. I believe a workaround for your situation would be to change the "-r" option of the test(1) utility to "-f" at line 9807 of the configure(1) script. This should allow the script to continue past this point with the correct idea about the logging system. > *Installing* is a different matter. > > Regards, > Harald Regards, Steve Emmerson Ticket Details =================== Ticket ID: PMU-379721 Department: Support LDM Priority: Normal Status: Closed