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

[netCDF #MBQ-177890]: RE: MinGW check failure

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: [netCDF #MBQ-177890]: RE: MinGW check failure
  • Date: Wed, 23 Feb 2011 16:24:22 -0700
> Ed,
> 
> When building I received the error:
> 
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../fortran -I../include 
> -I../l
> iblib -I../libsrc -MT v2i.lo -MD -MP -MF .deps/v2i.Tpo -c v2i.c  -DDLL_EXPORT 
> -D
> PIC -o .libs/v2i.o
> v2i.c: In function 'nvdims':
> v2i.c:39: error: 'NC' undeclared (first use in this function)
> 
> so I patched it with the v2i.c.patch file I've attached (note that the 
> location of v2i.c has changed from libsrc to libdispatch from verion 4.1.1 to 
> the current snapshot).
> 
> Now I get the following error:
> 
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../fortran -I../include 
> -I../l
> iblib -I../libsrc -I../libdispatch -I../oc -MT putget.lo -MD -MP -MF 
> .deps/putge
> t.Tpo -c putget.c  -DDLL_EXPORT -DPIC -o .libs/putget.o
> putget.c:3108: error: expected declaration specifiers or '...' before 'uint'
> 
> which I have to admit is perplexing; NC, NC_var, size_t, and uint have all 
> been used in previous functions, so they must have been defined, and there is 
> no conflicting function prototype.
> 
> Any ideas?
> 
> Thanks,
> Dan
> 

Howdy Dan!

Can you get the daily snapshot and try again? I'm pretty sure I fixed at least 
some of this problem...

ftp://ftp.unidata.ucar.edu/pub/netcdf/snapshot/netcdf-4-daily.tar.gz

Also, what configure options are you using?

To make things easy try turning off opendap with --disable-dap.

To make things REALLY easy, try turning off netCDF-4 with --disable-netcdf-4

Let me know how this comes out.

Thanks,

Ed

Ticket Details
===================
Ticket ID: MBQ-177890
Department: Support netCDF
Priority: Critical
Status: Closed