Release 1.6 (2006-06-19) adds various bug fixes, plus support for making
dimensions WITHOUT dimvars (coordinate variables), although I think this
is a bad idea in general. ALSO, the default behavior for put.var.ncdf
with unlimited variables and NO specified start and count parameters has
changed! Before, the default was to append to the end of the existing
variable. Now, the default is to assume a start of 1 along each
dimension, and a count of the current length of each dimension. This
really can be ambiguous when using an unlimited dimension. I always
specify both start and count when writing to a variable with an
unlimited dimension, and suggest you do as well. I make require this in
a future release, as it seems to cause people problems.
since they always need a C compiler, even when the source code is
completely in C++.
For some other packages, stated in the comment that a C compiler is
really not needed.
changes:
* Added support for constants e, log2(e), log10(e), ln(2), ln(10), pi,
pi/2, pi/4, 1/pi, 2/pi, 2/sqrt(pi), sqrt(2) and sqrt(1/2).
* Fixed bug with using global instead of evaluator specific symbol table
variable in evaluator_get_variables() function.
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
* Correct bug in configure script: --enable-portable-binary option was ignored!
* Threads compilation fix on AIX: prefer xlc_r to cc_r, and don't use
either if we are using gcc.
* Updated FAQ to note that Apple gcc 4.0.1 on MacOS/Intel is broken,
and suggest a workaround. configure script now detects Core/Duo arch.
* Use -maltivec when checking for altivec.h.
set OVERRIDE_DIRDEPTH to find any libtool scripts deeper in the WRKSRC
tree unless they're named something other than "libtool".
SHLIBTOOL_OVERRIDE generally doesn't need to be specified either -- just
define it to the empty list and shlibtool-override will look for libtool
scripts.
C libraries *before* we throw the AC_LANG([C++]) switch. This makes
the generated configure script use the C compiler/linker instead of
the C++ compiler/linker when running tests. This avoids errors like
these based on not correctly getting the function signature correct:
conftest.cc:36: error: nonnull argument with out-of-range operand
number (arg 1, operand 2)
This error was causing the configure script to not detect *gettext()
routines and not building and installing the *.mo files. This fixes
the error noted in the bulk build results:
http://mail-index.netbsd.org/pkgsrc-bulk/2006/06/20/0000.html
