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

Re: udunits and Windows

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: Re: udunits and Windows
  • Date: Wed, 15 Feb 2006 09:41:14 -0700
David,

>Date: Wed, 15 Feb 2006 14:38:58 +1300
>From: David Rupp <address@hidden>
>Organization: NIWA, New Zealand
>To: Steve Emmerson <address@hidden>
>Subject: Re: udunits and Windows

The above message contained the following:

> I've found someone here who knows her way around this windows compiler, 
> otherwise I don't think I could do this!

That's good news.

> I've managed to compile utparse.c, utscan.c, and udalloc.c.  However, I 
> get two warnings in utparse.c:
> 
> Compiling...
> utparse.c
> utparse.y(475) : warning C4013: 'utlex' undefined; assuming extern 
> returning int
> utparse.y(405) : warning C4102: 'yynewstate' : unreferenced label
> 
> utparse.obj - 0 error(s), 2 warning(s)
> 
> Shall I worry about them, or shall I keep trudging on?

I don't know.  I've never seen these warnings before.  I suspect that
the "utlex" warning may be safely ignored; I'm not sure about the
"yynewstate" one.  Still, the C compiler successfully created an object
file, so I'd be inclined to press on.

Regards,
Steve Emmerson