summaryrefslogtreecommitdiff
path: root/math/octave-forge
AgeCommit message (Collapse)AuthorFilesLines
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-3/+3
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
2005-10-27point to octave, not octave-currentdmcmahill1-2/+2
2005-10-26add buildlink3 file in anticipation of some new packages which will need itdmcmahill1-0/+20
2005-08-23remove leftover patch which is no longer useddmcmahill2-10/+1
2005-08-06Fixed an undefined reference to close(2).rillig2-1/+16
2005-08-04Changes 2005-06-13:adam11-184/+80
* textread now returns cell arrays * use new gnuplot interface for functions * fix rand bug on non-intel architectures * more econometrics functions * new functions: randg, cellfun, cell2mat, bwarea, imresize, savepath * bug fixes and improvements (see ChangeLog for details)
2005-06-01Massive cleanup of buildlink3.mk and builtin.mk files in pkgsrc.jlam1-2/+2
Several changes are involved since they are all interrelated. These changes affect about 1000 files. The first major change is rewriting bsd.builtin.mk as well as all of the builtin.mk files to follow the new example in bsd.builtin.mk. The loop to include all of the builtin.mk files needed by the package is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk is now included by each of the individual builtin.mk files and provides some common logic for all of the builtin.mk files. Currently, this includes the computation for whether the native or pkgsrc version of the package is preferred. This causes USE_BUILTIN.* to be correctly set when one builtin.mk file includes another. The second major change is teach the builtin.mk files to consider files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most of the builtin.mk files test for the presence of built-in software by checking for the existence of certain files, e.g. <pthread.h>, and we now assume that if that file is under ${LOCALBASE}, then it must be from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The exceptions to this new check are the X11 distribution packages, which are handled specially as noted below. The third major change is providing builtin.mk and version.mk files for each of the X11 distribution packages in pkgsrc. The builtin.mk file can detect whether the native X11 distribution is the same as the one provided by pkgsrc, and the version.mk file computes the version of the X11 distribution package, whether it's built-in or not. The fourth major change is that the buildlink3.mk files for X11 packages that install parts which are part of X11 distribution packages, e.g. Xpm, Xcursor, etc., now use imake to query the X11 distribution for whether the software is already provided by the X11 distribution. This is more accurate than grepping for a symbol name in the imake config files. Using imake required sprinkling various builtin-imake.mk helper files into pkgsrc directories. These files are used as input to imake since imake can't use stdin for that purpose. The fifth major change is in how packages note that they use X11. Instead of setting USE_X11, package Makefiles should now include x11.buildlink3.mk instead. This causes the X11 package buildlink3 and builtin logic to be executed at the correct place for buildlink3.mk and builtin.mk files that previously set USE_X11, and fixes packages that relied on buildlink3.mk files to implicitly note that X11 is needed. Package buildlink3.mk should also include x11.buildlink3.mk when linking against the package libraries requires also linking against the X11 libraries. Where it was obvious, redundant inclusions of x11.buildlink3.mk have been removed.
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam1-2/+2
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-05-22fix the category. this is math not cad...dmcmahill1-2/+2
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-04-01Use math/octave, not octave-currentadam1-7/+9
2005-03-19use awk instead of csplit during the build. csplit was onlydmcmahill3-15/+11
used in one place and it generated a build dependency on a package which conflicts with many other pkgs.
2005-03-16We no longer have to explicitly set F77. Addresses PR29666dmcmahill1-2/+1
2005-03-14- don't hard code /bin/sh (use the configured shell). Needed todmcmahill7-2/+97
get a working shell on solaris. - fix a header file - avoid passing invalid parameters to mkoctfile. octave-forge now works on solaris too.
2005-03-13remove some non-portable shell constructsdmcmahill2-1/+15
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2004-12-05Changes 2004.11.16:adam11-203/+98
* initial econometrics toolbox * updated protein databank (extra/pdb) functions * new functions: wavread wavwrite hann strfind randp sprandn conv2nan * many bug fixes and improvements
2004-12-03Rename ALL_TARGET to BUILD_TARGET for consistency with other *_TARGETs.wiz1-2/+2
Suggested by Roland Illig, ok'd by various.
2004-10-30Update to octave-forge-2004.09.09. The most notable change is that thisdmcmahill13-759/+721
version now works with octave-current-2.1.59 which is what's currently in pkgsrc. Other than than, many minor bug fixes.
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-1/+2
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.
2004-09-03Turn off the "fixed" module for now as it won't compile with the toolchaindmcmahill2-42/+7
in NetBSD-current. It may not be too hard for a c++ programmer to fix. Should address recently noted bulk build failures.
2004-08-14import octave-forge-2004.07.07dmcmahill14-0/+1788
The octave-forge project contains functions for Octave which are not in the main distribution. While the main Octave distribution is conservative about accepting new functions and changes, octave-forge is very open. As a result, be prepared for some lower quality code and more rapidly changing interfaces to the functions in octave-forge.