library changes require configure.in update

[Charlie Zender]

Hi Rorik,

Please add nco_rth_flt.[ch] to libnco in the autotools source.
ncap_utl.o should not be in libnco (I'm not sure if it is, please
check).  The recent changes to bld/Makefile allow NCO
to be built natively on MAC OS X on the sourceforge compile
farm, so now I'd like to get configure caught up.

Also, are DODS builds working for you under Linux?
They do not for me.
I tried modifying configure.in to check for the actual routines
stored in some of the DODS libraries and I ended up puzzled
because when I changed configure.in to look for a routine
that was actually in librx.a instead of look for main(), things
got worse.

Thanks,
Charlie

[Rorik Peterson]

I added nco_rth_flt.[ch] to the library build.

I tinkered around again with --enable-dods.  It works on my Linux machine.  I added a test that will run with 'make check' only when DODS is enabled.  It is simply the example in the documentation under DODS.

Upload the config.log, make output, etc. to dust and I can take a look at why it isn't working (if it still is not).

rorik

[Charlie Zender]

Thanks, I tried a DODS build on my machine and
you can see the results are not good. There seems
to be version mismatch between the C++ libraries
that DODS links to. It's possible that my gcc installation
is not correct, so I'm not going to sweat this if it works
for you. I might switch to Debian soon. But if you are
interested in trying to resolve some of the problems in getting builds working on the sourceforge compile farm
(Sun, FreeBSD, MacOS X) that would be helpful.
The status of these builds is in configure.eg and some
of the required scripts are in nco_srg_frg.txt.

Is there a standalone shell command to determine the
GNU triplet of the host machine? i.e., i686-pc-linux-gnu, or is that deeply embedded within configure?

Thanks,
Charlie

[Rorik Peterson]

It is simply a shell script that comes with autoconf; run/see autobld/config.guess

rorik