[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20040813: building UDUNITS on Cygwin

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.

  • Subject: 20040813: building UDUNITS on Cygwin
  • Date: Fri, 13 Aug 2004 14:36:15 -0600
Dipesh,

>Date: Fri, 13 Aug 2004 13:34:04 -0700
>From: Dipesh Patel <address@hidden>
>Organization: USDA
>To: "'Steve Emmerson'" <address@hidden>
>Subject: 20040813: building UDUNITS on Cygwin 
> Keywords: 200408131907.i7DJ7QaW021117 UDUNITS

The above message contained the following:

>       I got past the error I just sent you.  It is trying to use the @CXX@
> because in Cygwin, the files are case insensitive.  There is a target in the
> udunits/Makefile that was:
> 
> dummy_prog $(PROGRAM):        $(OBJS)
>       @if [ -r $@.f -o -r $@.F ]; then \
>           ld='$(FC) -o $@ $(FFLAGS)'; \
>       elif [ -r $@.cc -o $@.C ]; then \
>           ld='$(CXX) -o $@ $(CXXFLAGS)'; \
>       else \
>           ld='$(CC) -o $@ $(CFLAGS)'; \
>       fi; \
>       cmd="$$ld $(LDFLAGS) $(OBJS) $(LIBS)"; \
>       echo $$cmd; \
>       $$cmd \
>           || (rm -f $@; exit 1)
> 
> But, since Cygwin is case insensitive, the first elif evaluates to true
> because there is a corresponding .c file.  I took out the "-o $@.C" part of
> the first elif clause, and I got past that error. And the library builds -
> but I still get the 1 second off problem.

Ah, the joys of non-conformance to the UNIX Standard.  :-)

Good catch.

> I have been putting the -Df2cFortran flag in CFLAGS, but I'm not sure what
> that does.

It makes it possible to build a Fortran interface to the UDUNITS
package.

> I had to put that in to get it to compile.  But, you are right,
> there is something going wrong still.  I will try the 1.12.1 version next.

Let me know.

Regards,
Steve Emmerson