developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
Fixed a bug reported by the sourceforge user: cedars where:
ln(exp(6)) == 3 /* WRONG!!! */
incorrectly returned 1. This bug was fixed by Ernest Bowen
The regression test was expanded to cover this issue.
Added minor improvements to hash regression testing of pi().
Fixed "help script" and the calc man page regarding the requirement
of -f to be the last -flag in shell script mode. Further clarified
the meaning and placement of the -f flag.
Moved issues with chi.cal intfile.cal into a "mis-features" section
of the BUGS file. See "help bugs" or the BUGS source file for details.
Added the bug about:
calc 'read ellip; efactor(13*17*19)'
to the BUGS file. See "help bugs" or the BUGS source file for details.
Anyone want to track down and fix this bug?
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
This release adds changes to better support compiling under cygwin,
improved custom function support, including the addition of the
pmodm127 example and config("compile_custom") and config("allow_custom")
calls, and a missing display help file. It fixes configuration
state hashing, document typos, calc -d (to disable printing of the
leading ~), and some compilation warnings reported under OS X.
This release fixes a bug related to post incrementing, some regression failures related to compiling under cygwin, and a number of gcc compiler warnings.
Fixed calc man page examples to move -f to the end of the line.
Thanks goes to Michael Somos <somos at grail dot cba dot csuohio
dot edu> for pointing this out.
Linux and gcc now compiled with -Wall -W -Wno-comment.
Fixed a post increment that was reported by R. Trinler <trinler at
web dot de> and fixed by Ernest Bowen <ernie at turing dot une dot
edu dot au>.
Fixed pi.cal to not depend on the buggy pre-2.11.9 post increment
behavior.
Added config("cygwin") to determine if calc was compiled under Cygwin.
The config("cygwin") is a read-only configuration value that is 1
when calc was compiled under Cygwin and 0 otherwise. Regression
tests 949 and 950 are skipped when config("cygwin") is true.
The Makefile variable HAVE_NO_IMPLICIT is empty by default so that
the Makefile will test if the compiler has a -Wno-implicit flag.
Added HAVE_UNUSED Makefile variable. If HAVE_UNUSED is empty,
then the Makefile will run the have_unused program to determine
if the unused attribute is supported. If HAVE_UNUSED is set to
-DHAVE_NO_UNUSED, then the unused attribute will not be used.
The Makefile builds have_unused.h which defines, if the unused
attribute is supported:
#define HAVE_UNUSED /* yes */
#define UNUSED __attribute__((unused)) /* yes */
or defines, if the unused is not supported (or if the Makefile
variable is HAVE_UNUSED= -DHAVE_NO_UNUSED):
#undef HAVE_UNUSED /* no */
#define UNUSED /* no */
Fixed numerous warnings about comparison between signed and unsigned
value warnings and unused parameter warnings in version.c, zrand.c,
string.c, shs1.c, shs.c, qtrans.c, qmath.c, qfunc.c, md5.c, matfunc.c,
hist.c, file.c, const.c, blkcpy.c, seed.c, opcodes.c, func.c, qio.c,
zrandom.c, custom/c_argv.c, custom/c_devnull.c, custom/c_help.c,
custom/c_sysinfo.c, addop.c and calc.c.
Fixed some typos in this file.
By default, compile with -O3 -g3. The Makefile comments on how some
distributions might need to use -O2 -g or -O -g.
curses.buildlink2.mk. This was wrong because we _really_ do want to
express that we want _n_curses when we include the buildlink2.mk file.
We should have a better way to say that the NetBSD curses doesn't
quite work well enough. In fact, it's far better to depend on ncurses
by default, and exceptionally note when it's okay to use NetBSD curses
for specific packages. We will look into this again in the future.
Clarify that the internal hash as well as the hash builtin
function used by calc, while based on the Fowler/Noll/Vo
hash is NOT an FNV hash.
Made slight performance improvements to calc by an optimization of how
calc's internal hash is computed. The "make chk" regression test
runs about 1.5% faster (when compiled with -O3 on an AMD Athlon)
NO_HASH_CPU_OPTIMIZATION is not defined. Calc's internal hash values
have not changed. By default, NO_HASH_CPU_OPTIMIZATION is NOT defined
and the slightly faster expression is used.
A slight modification of what was known as the "calc new stardard"
configuration (calc -n or config("all", "newstd")) is now the default
calc configuration. The flag:
calc -O
was added to get the old classic calc configuration. The flag command
line flag, -n, now does nothing. Use of -n is deprecated and may go
away / be used for something else in the future.
The following table gives the summary of these changes:
pre v2.11.8 v2.11.8
default pre v2.11.8 -O & oldstd v2.11.8
and oldstd -n & newstd classic cfg default
--------------------------------------------------------
epsilon 1e-20 1e-10 1e-20 1e-20
quo 2 2 2 2
outround 2 24 2 24
leadzero 0 1 0 1
fullzero 0 1 0 0
prompt > ; > ;
more >> ;; >> ;;
With the exception of epsilon being 1e-20, and fullzero being unset,
the new default calc config is like it was (pre-2.11.8) with calc -n /
config("all", "newstd").
The new default config is the old classic config with outround being
24, leadzero being set, and the prompts being ;'s.
CXXFLAGS, and LDFLAGS by the buildlink.mk files so remove the extra
definitions to add them from the package Makefiles. As advised by the
bsd.buildlink.mk file, also ensure that the buildlink.mk files are
included prior to defining any package-specific CFLAGS/LDFLAGS to ensure
that the buildlink directories are at the head of the compiler search
paths.
Use BUILDLINK_INCDIR, BUILDLINK_LIBDIR for locations of linked headers
and libraries. Create a variable BUILDLINK_TARGETS whose value is the
list of build-link targets to execute.
