Re: [Opengrads-devel] Solaris build

[Arlindo da S. <da...@al...>]

On Jan 26, 2008 12:50 AM, Don Hooper <ho...@co...> wrote:

> Arlindo,
>
> I'm very confused.  The configure output doesn't mention netCDF4,
> yet it insists on trying to build it anyway.


Strange. When I type 'configure --help' I get

---cut---
Optional Packages:
  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
  --with-readline         command line editing via readline
  --with-printim          printim command - image output using GD
  --with-lats             LATS interface for generating GRIB and netCDF
files
  --with-gui              Athena X11 widget-based GUI
  --with-nc               gradsnc executable, with netCDF-3 support
  --with-nc4              gradsnc executable, with netCDF-4 support
  --with-dods             gradsdods executable, with netCDF and OPeNDAP
                          support
---cut---


> Beyond that, I'm
> not sure what you mean by "all other extensions should build"; I
> saw nothing but the usual GrADS binaries build.  I didn't see gxyat
> at all.  The bin-dist tarball and the gex-dist tarball are identical.
> I must really be missing something.  The make check was odd, too.  It
> only ran in pytests and failed utterly there.  It claimed there was
> nothing to do for target "check" in src.  I'm very confused....
>

OK, you may have found a bug in our 'make dist' which creates the src tar
ball. The extensions/ directory, I forgot, is not included with that (we
wanted to retain a vanilla COLA look and feel and handle extensions
separately). We have a module "Grads" which adds the extensions/ directory
to it.

> Also, I don't have a sf username.
OK, if you ever get one let me know I'll add you as a developer (the
sf.netregistration URL is
https://sourceforge.net/account/registration/). In the mean time, your best
bet is to check anonimously the module Grads from the repo (notice capital
"G"):


cvs -d:pserver:ano...@op...:/cvsroot/opengrads
login

cvs -z3 -d:pserver:ano...@op...:/cvsroot/opengrads
co -P *Grads*

*See whether building with this would work. I am more concerned about you
being able to have "make check" working as it has been extremely useful
detecting problems in the binaries. BTW, it only requires plain python, but
it may not work with a very old version. Enter "python" and check the
version; v2.3 and newer should be fine.*

*   Thanks,*

*      Arlindo*

**

**

**

**




>
> -Hoop
>
> > From arl...@gm...  Fri Jan 25 20:58:48 2008
>  >
> > On Jan 25, 2008 7:35 PM, Don Hooper <ho...@co...> wrote:
> >
> > > Arlindo,
> > >
> > > I'm not sure just what I've accomplished.  I built your supplibs
> tarball
> > > (the trick was not only GNU's make, but getting it to use bash, as in:
> > >        gmake SHELL=/bin/bash install
> > > ).  Then, I could build everything in your GrADS tarball
> >
> > This is great! NetCDF4 is just an experimental version to see whether it
> is
> > ready for prime time. So far gradsnc4 has been passing all tests in all
> > platforms.
> >
> > I just posted the frozen grads 1.9.0-rc1 sources on
> >
> >      http://opengrads.org/pre-rel
> >
> > Untar the sources alongside the supplibs then
> >
> > ./configure   (all should be enabled except wi and gradsnc4)
> > make
> > make check  (to run the test suite)
> > make bin-dist  (create binary tarball)
> > make gex-dist  (for the extension tarball)
> >
> > Unless you have cairo around, gxyat may not build but all other
> extensions
> > should build (make sure g77 is present). Check the documentation at the
> > wiki. I'm slowly completing the documentation but would appreciate any
> > feedback on what is there. You should have a login for the wiki. If you
> see
> > anything needs editing feel free to jump in and make corrections (you
> need
> > to be logged on to be able to edit it).
> >
> > > except the nc4
> > > version, as your supplibs tarball didn't seem to have code for netcdf4
> > > libraries, etc.
> >
> > Strange, I must have messed up making the src tarball. I'll refresh the
> > sources. However, if you send me your sf.net username I can give you
> commit
> > privileges to the repository so you check a fresh copy yourself.
> >
> > BTW, in the supplibs page at the wiki I am maintaining a section on
> platform
> > specific notes. I'd be interested in having some notes on your tweaks
> for
> > the solaris build.
> >
> > > I guess I need to download more source to do any of
> > > the extensions, like PyGrADS, right?
> >
> > Not really. PyGrADS is 100% python, the core package even works under
> jython
> > with the java vm.  For taking full advantage of it you must have a
> capable
> > python installation. Basically, make sure you have Matplotlib with the
> > basemap toolkit installed. I have the latest pygrads tarball in the same
> > pre-rel site above. Untar and take a look at the README. Installation is
> > really easy, and the minimum requirement is python. If you have
> matplotlib
> > then you can use it for graphics; if you have numpy you can do EOFs and
> > least square estimation. In the very least you should be able to use it
> to
> > script grads. See the examples directory.
> >
> > BTW, I am making a somewhat artificial distinction between "extensions"
> and
> > "interfaces". Extensions are user defined commands and user defined
> > functions implemented as shared objects; so it seats below grads.
> Interfaces
> > are basically written at the host interpreted language (perl, python,
> even
> > IDL), so it seats above grads.
> >
> > So, whenever you have your solaris binaries I'd be glad to post them on
> > sf.net. Just make sure they pass the test suite (make check). And feel
> free
> > to introduce additional test cases --- I just did the bare minimum.
> >
> > Thank you very much for the help with the solaris build.
> >
> >   Best Regards,
> >
> >       Arlindo
> > --
> > Arlindo da Silva
> > da...@al...
>



-- 
Arlindo da Silva
da...@al...