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

[netCDF #PPH-319693]: Problem building NetCDF 64-bit versions on AIX

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 #PPH-319693]: Problem building NetCDF 64-bit versions on AIX
  • Date: Wed, 05 Oct 2011 19:53:41 -0600
Peter,

> Thanks for the confirmation. Would it be possible to document this
> somewhere, for example in the operating specific instruction FAQ.

Yes, I've fixed the online HTML installation guide, and it will also be fixed 
in the 
documentation bundled in the next release.  Thanks for reporting the
problem!

   
http://www.unidata.ucar.edu/software/netcdf/docs/netcdf-install/Platform-Notes.html#Platform-Notes

--Russ

> From:   "Unidata netCDF Support" <address@hidden>
> To:     Peter Farrell/Australia/IBM@IBMAU
> Cc:     address@hidden
> Date:   06/10/2011 07:50 AM
> Subject:        [netCDF #PPH-319693]: Problem building NetCDF 64-bit
> versions on AIX
> 
> 
> 
> Hi Peter,
> 
> > I'm trying to build a 64-bit version of NetCDF.
> >
> > The OS version is AIX 6.1. NetCDF is version netcdf-4.1.3.
> >
> > The problem arises when trying to use ar to insert object modules into
> > libraries. The object modules are 64-bit but the command (ar) is
> expecting
> > 32-bit objects.
> >
> > Various documentation states that there is a requirement to use ARFLAGS=
> > "-X64 cru"
> > This should work but did not. I then set OBJECT_MODE=64 which did result
> > in a successful compilation.
> >
> > On investigation, I discovered that despite the environment variable
> being
> > set, the makefiles all use flags of "cru". I did not discover where this
> > was coming from but I did notice that other compiler flags such as
> CFLAGS
> > were propagated from the environment into the makefile, unlike ARFLAGS.
> >
> > It would seem that there is a bug or oversight in configure.
> 
> Yes, this is a known problem with libtool that has been around for a
> while:
> 
> 
> http://www.unidata.ucar.edu/software/netcdf/docs/known_problems.html#ARFLAGS
> 
> 
> The only solution we know about is to use AR_FLAGS instead of ARFLAGS, or
> as you have already discovered, to set OBJECT_MODE=64.
> 
> --Russ
> 
> 
> Russ Rew                                         UCAR Unidata Program
> address@hidden                      http://www.unidata.ucar.edu
> 
> 
> 
> Ticket Details
> ===================
> Ticket ID: PPH-319693
> Department: Support netCDF
> Priority: Normal
> Status: Closed
> 
> 
> 
> 

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: PPH-319693
Department: Support netCDF
Priority: Normal
Status: Closed