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

Re: 20050822:netCDF Fortran (77 + 90) - configure does not support .obj files

Unidata Support <address@hidden> writes:

> ------- Forwarded Message
>
>>To: address@hidden
>>From: "David Offiler" <address@hidden>
>>Subject: netCDF Fortran (77 + 90) - configure does not support .obj files
>>Organization: UCAR/Unidata
>>Keywords: 200508221459.j7MExPV5023152
>
> Institution: Met Office (UK)
> Package Version: 3.6.1-Beta3
> Operating System: Cygwin on Windows XP Pro
> Hardware Information: Dell P4 2.6GHz
> Inquiry: Attempting to build netCDF (3.6.1-Beta3) under Cygwin using the 
> Intel Visual Fortran V8.1 compiler ('ifort') with Microsoft Visual C++ .NET 
> ('cl'). Both compilers only output '.obj' files, not '.o'.
>
> While the configure script detects that the latter outputs .obj, it ignores 
> this information - throughout there are explicit references for <file>.o 
> which cause errors of the 'file not found' variety (because both C & F 
> compiled - successfully- to <file>.obj).
>
> Is there any release which supports this behaviour, and if not, could it be 
> considered for a future one. Thx.
>
> PS - successful builds have been done with g95 & gfortran (and several others 
> on Linux & HP-UX); we are writing portable applications and need to prove 
> that builds work from scratch.
>
>

Howdy!

It's true that using MS VC++ as the compiler with Cygwin is not one of
our currently supported combinations. I would like it to be, but it's
not.

Have you tried using the .sln files to compile netCDF within visual
studio?

Or can you patch the configure.ac file to make this work? If so, I
could incorporate your patches.

I sense that this would not be too difficult to do, but there is a
long list of development tasks that have a higher priority right now -
we are working on a major upgrade, to netCDF 4.0.

So I'm afraid there are no immediate plans to get this working, but if
you can figure it out, I would be happy to incorporate the changes
into future releases.

Thanks,

Ed
-- 
Ed Hartnett  -- address@hidden