This list is closed, nobody may subscribe to it.
2000 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(10) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
(4) |
Mar
|
Apr
(3) |
May
(13) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
(2) |
Oct
(5) |
Nov
(8) |
Dec
|
2002 |
Jan
|
Feb
|
Mar
(19) |
Apr
(8) |
May
(8) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(19) |
Oct
(13) |
Nov
(37) |
Dec
(2) |
2003 |
Jan
(7) |
Feb
(23) |
Mar
(16) |
Apr
(4) |
May
(18) |
Jun
(9) |
Jul
(7) |
Aug
(6) |
Sep
(7) |
Oct
|
Nov
(39) |
Dec
(57) |
2004 |
Jan
(21) |
Feb
(15) |
Mar
(17) |
Apr
(9) |
May
(17) |
Jun
(65) |
Jul
(33) |
Aug
(48) |
Sep
(93) |
Oct
(35) |
Nov
(18) |
Dec
(4) |
2005 |
Jan
(20) |
Feb
(59) |
Mar
(17) |
Apr
(59) |
May
(77) |
Jun
(32) |
Jul
(34) |
Aug
(8) |
Sep
(34) |
Oct
(26) |
Nov
(65) |
Dec
(66) |
2006 |
Jan
(45) |
Feb
(37) |
Mar
(50) |
Apr
(32) |
May
(48) |
Jun
(42) |
Jul
(12) |
Aug
(53) |
Sep
(51) |
Oct
(79) |
Nov
(46) |
Dec
(25) |
2007 |
Jan
(120) |
Feb
(78) |
Mar
(45) |
Apr
(91) |
May
(155) |
Jun
(66) |
Jul
(96) |
Aug
(110) |
Sep
(145) |
Oct
(189) |
Nov
(68) |
Dec
(160) |
2008 |
Jan
(163) |
Feb
(212) |
Mar
(209) |
Apr
(157) |
May
(216) |
Jun
(120) |
Jul
(80) |
Aug
(83) |
Sep
(98) |
Oct
(120) |
Nov
(80) |
Dec
(129) |
2009 |
Jan
(45) |
Feb
(80) |
Mar
(174) |
Apr
(142) |
May
(133) |
Jun
(191) |
Jul
(183) |
Aug
(138) |
Sep
(77) |
Oct
(141) |
Nov
(209) |
Dec
(131) |
2010 |
Jan
(85) |
Feb
(213) |
Mar
(245) |
Apr
(222) |
May
(168) |
Jun
(82) |
Jul
(50) |
Aug
(144) |
Sep
(92) |
Oct
(80) |
Nov
(64) |
Dec
(78) |
2011 |
Jan
(58) |
Feb
(98) |
Mar
(112) |
Apr
(98) |
May
(64) |
Jun
(150) |
Jul
(126) |
Aug
(59) |
Sep
(271) |
Oct
(154) |
Nov
(321) |
Dec
(183) |
2012 |
Jan
(146) |
Feb
(217) |
Mar
(426) |
Apr
(208) |
May
(206) |
Jun
(230) |
Jul
(158) |
Aug
(170) |
Sep
(237) |
Oct
(260) |
Nov
(178) |
Dec
|
From: Per P. <per...@ma...> - 2003-05-21 07:46:19
|
Hi, finally back from the realm of the living dead to work on fun stuff! > * administration: > - target specific build instructions (MacOSX, windows, Irix) I'm looking over the build instructions for MacOSX right now. There is one thing that I'd like to fix, but really don't know how to without risk of breaking stuff. The flags -fdp in "cp -fdp $files $opath" in octinst.sh needs to be replaced by -Rfp on OS X (and probably *BSD too??). A variable COPY_FLAGS or some such in configure to substitute in octinst.sh.in would perhaps be the best solution? Comments? /Per |
From: Paul K. <pki...@us...> - 2003-05-21 02:48:46
|
David Bateman wrote: >At this point I haven't made a test to see whether perl is installed, >but if it isn't you are bound to have other problems in the admin >directory... Is it worth disabling the build of comms.texi from >comms.txi if perl is not found? If so shoudl the test for perl be >made in configure.base or in main/comm/configure.add? > I'm inclined to assume perl for now, but minimize its use. The only systems that won't have perl readily available are probably windows systems, and most of those folks will be using prebuilt octave/octave-forge. - Paul BTW, thanks for the makefile updates. |
From: David B. <Dav...@mo...> - 2003-05-20 15:53:34
|
> I just checked out the source from CVS, and the only problem I saw so far > was that the make file specified a file main/comm/comm.texi, but the file > was named comm.txi. I renamed the texinfo file and the build completed > successfully, but I notice that the help files seem screwed up. That > might be something to check into. Please don't do this!!! comms.texi is made from comms.txi, including all of the help from all of the functions in the package in a similar manner to octave itself. The function that does this is the perl script mktexi which is also included in main/comm. You do have perl installed ? From comms.texi the files comms.ps, comms.pdf, comms*.html and comms.info can be made with the texi2dvi + dvips, texi2dvi + pdvpdf, texi2html and texinfo programs. These require texinfo and tex to be installed. I recently checked in changes to the Makefile scripts that will disable the building and installation of these files if you don't have the texinfo and tex packages installed. So I hope that if you re-checkout octave-forge and don't change the name of comm.txi everything should work fine... At this point I haven't made a test to see whether perl is installed, but if it isn't you are bound to have other problems in the admin directory... Is it worth disabling the build of comms.texi from comms.txi if perl is not found? If so shoudl the test for perl be made in configure.base or in main/comm/configure.add? D. -- David Bateman Dav...@mo... Motorola CRM +33 1 69 35 25 00 (Ph) Espace Technologique, Commune de St Aubin +33 1 69 35 25 01 (Fax) 91193 Gif-Sur-Yvette FRANCE The information contained in this communication has been classified as: [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary |
From: Chris C. <ch...@ch...> - 2003-05-20 03:37:11
|
> That should be fixed now. Please let me know if the current > CVS works for you. I plan to release it RSN. It should > compile for 2.1.36 and up. I just checked out the source from CVS, and the only problem I saw so far was that the make file specified a file main/comm/comm.texi, but the file was named comm.txi. I renamed the texinfo file and the build completed successfully, but I notice that the help files seem screwed up. That might be something to check into. "make icheck" failed the very first test due to "gget" being unavailable. Not sure what that is about, but gset works correctly. I have never used gget in any of my scripts, so I don't have a test case to check it with. Mex files compile OK. I'm still doing some regression testing, but the octave forge stuff looks OK so far. The version of octave shipped with the new Red Hat 9 has some weirdness loading script files, but I haven't figured out exactly what it is complaining about. system configuration: Red Hat 9 gcc 3.2.2 Octave 2.1.40 from Red Hat rpm octave-forge checked out from CVS 18 May thanks, Chris Caudle |
From: Etienne G. <et...@is...> - 2003-05-16 07:29:21
|
Hello, maybe we could put an entry for 'vmesh' in the INDEX file, under 'Surface plots'. Cheers, Etienne On Thu, May 15, 2003 at 05:34:35PM -0400, Paul Kienzle wrote: # All, # # We need a new release to support octave-2.1.48 since # OCTAVE_LOCAL_BUFFER now requires #include <memory>. # I've updated the half-dozen files that require it # (inc. comm/gf.cc and sparse/make_sparse.h). # # Here is my take on the changes since the last release. # Please correct any errors in octave-forge/RELEASE-NOTES # # * Support for octave 2.1.36-2.1.48. # # * Communications: # - sqrt over Galois field # - BCH code, modulator # - bug fixes and documentation improvements # # * Image: # - add rotate_scale() # # * Optimization: # - add Nick Higham's adsmax, mdsmax nmsmax for fmins # - lp() fix range error # # * Plotting: # - surf()/surfc() support gnuplot 3.8i shaded surfaces # - add peaks() # - legend() inside/ouside/boxon/boxoff/right/left # # * Signal Processing # - return statespace and laplacian IIR filters (butter, cheby1, cheby2, ellip) # - fix aryule # # * Statistics: # - add normplot() # - scatter() optimization # # * Symbolic: # - added poly2sym, sym2poly, numden, findsymbols, findsym, symlsolve, # symfsolve, syminfo # - subs() accepts cell arrays # # * TSA/NaN: # - many bug fixes and documentation improvements # - quantiles -> Quantile # # * Miscellaneous: # - add cellstr() # - fieldnames() now returns cell array # - listen() bugfixes # - ellipke() supports m < 0 # - extend deal() to handle [a,b] = deal(b,a) # - dlmread() converted to C++ for speed and more flexible input # # * administration: # - target specific build instructions (MacOSX, windows, Irix) # # # # ------------------------------------------------------- # Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara # The only event dedicated to issues related to Linux enterprise solutions # www.enterpriselinuxforum.com # # _______________________________________________ # Octave-dev mailing list # Oct...@li... # https://lists.sourceforge.net/lists/listinfo/octave-dev # # -- Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne |
From: Paul K. <pki...@ja...> - 2003-05-15 21:34:38
|
All, We need a new release to support octave-2.1.48 since OCTAVE_LOCAL_BUFFER now requires #include <memory>. I've updated the half-dozen files that require it (inc. comm/gf.cc and sparse/make_sparse.h). Here is my take on the changes since the last release. Please correct any errors in octave-forge/RELEASE-NOTES * Support for octave 2.1.36-2.1.48. * Communications: - sqrt over Galois field - BCH code, modulator - bug fixes and documentation improvements * Image: - add rotate_scale() * Optimization: - add Nick Higham's adsmax, mdsmax nmsmax for fmins - lp() fix range error * Plotting: - surf()/surfc() support gnuplot 3.8i shaded surfaces - add peaks() - legend() inside/ouside/boxon/boxoff/right/left * Signal Processing - return statespace and laplacian IIR filters (butter, cheby1, cheby2, ellip) - fix aryule * Statistics: - add normplot() - scatter() optimization * Symbolic: - added poly2sym, sym2poly, numden, findsymbols, findsym, symlsolve, symfsolve, syminfo - subs() accepts cell arrays * TSA/NaN: - many bug fixes and documentation improvements - quantiles -> Quantile * Miscellaneous: - add cellstr() - fieldnames() now returns cell array - listen() bugfixes - ellipke() supports m < 0 - extend deal() to handle [a,b] = deal(b,a) - dlmread() converted to C++ for speed and more flexible input * administration: - target specific build instructions (MacOSX, windows, Irix) |
From: Chris C. <ch...@ch...> - 2003-05-14 03:28:02
|
What version of gcc is typically used to compile and test the latest version? Using gcc 3.2.2 I got the errors included below. The transition from gcc 3.1 to gcc 3.2 caused problems for a lot of apps because of being more strict about language usage, any chance that is what is going on here? This is on a Red Hat 9 system with the Red Hat compiled 2.1.40 -- Chris Caudle ----- compile error log: mex.cc: In function `octave_value_list call_mex(callstyle, const octave_value_list&, int)': mex.cc:504: parse error before `*' token mex.cc:505: parse error before `*' token mex.cc:506: `argin' undeclared (first use this function) mex.cc:506: (Each undeclared identifier is reported only once for each function it appears in.) mex.cc:507: `argout' undeclared (first use this function) make[2]: *** [mex.o] Error 1 make[1]: *** [mex/] Error 2 make: *** [extra/] Error 2 ----- configure log: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. configure:551: checking for gcc configure:664: checking whether the C compiler (gcc ) works configure:680: gcc -o conftest conftest.c 1>&5 configure:706: checking whether the C compiler (gcc ) is a cross-compiler configure:711: checking whether we are using GNU C configure:720: gcc -E conftest.c configure:739: checking whether gcc accepts -g configure:777: checking for mkoctfile configure:915: checking for F77_FUNC configure:923: mkoctfile -c conftest.cc configure:934: checking for octave configure:963: checking whether ln -s works configure:1014: checking for a BSD compatible install configure:1069: checking for ranlib configure:1101: checking for strip configure:1133: checking how to run the C preprocessor configure:1154: i386-redhat-linux-gcc -E conftest.c >/dev/null 2>conftest.out configure:1217: checking for X configure:1531: checking for dnet_ntoa in -ldnet configure:1550: i386-redhat-linux-gcc -o conftest -O2 -march=i386 -mcpu=i686 -g conftest.c -ldnet 1>&5 /usr/bin/ld: cannot find -ldnet collect2: ld returned 1 exit status configure: failed program was: #line 1539 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ /* We use char because int might match the return type of a gcc2 builtin and then its argument prototype would still apply. */ char dnet_ntoa(); int main() { dnet_ntoa() ; return 0; } configure:1572: checking for dnet_ntoa in -ldnet_stub configure:1591: i386-redhat-linux-gcc -o conftest -O2 -march=i386 -mcpu=i686 -g conftest.c -ldnet_stub 1>&5 /usr/bin/ld: cannot find -ldnet_stub collect2: ld returned 1 exit status configure: failed program was: #line 1580 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ /* We use char because int might match the return type of a gcc2 builtin and then its argument prototype would still apply. */ char dnet_ntoa(); int main() { dnet_ntoa() ; return 0; } configure:1620: checking for gethostbyname configure:1648: i386-redhat-linux-gcc -o conftest -O2 -march=i386 -mcpu=i686 -g conftest.c 1>&5 configure:1718: checking for connect configure:1746: i386-redhat-linux-gcc -o conftest -O2 -march=i386 -mcpu=i686 -g conftest.c 1>&5 configure:1810: checking for remove configure:1838: i386-redhat-linux-gcc -o conftest -O2 -march=i386 -mcpu=i686 -g conftest.c 1>&5 configure:1902: checking for shmat configure:1930: i386-redhat-linux-gcc -o conftest -O2 -march=i386 -mcpu=i686 -g conftest.c 1>&5 configure:2003: checking for IceConnectionNumber in -lICE configure:2022: i386-redhat-linux-gcc -o conftest -O2 -march=i386 -mcpu=i686 -g -L/usr/X11R6/lib conftest.c -lICE 1>&5 configure:2394: checking for linux/soundcard.h configure:2404: i386-redhat-linux-gcc -E conftest.c >/dev/null 2>conftest.out configure:2449: checking for qh_qhull in -lqhull configure:2467: i386-redhat-linux-gcc -O2 -march=i386 -mcpu=i686 -g conftest.c -o conftest -lqhull conftest.c:2:25: qhull/qhull.h: No such file or directory configure:2507: checking for jpeglib.h configure:2517: i386-redhat-linux-gcc -E conftest.c >/dev/null 2>conftest.out configure:2513:21: jpeglib.h: No such file or directory configure: failed program was: #line 2512 "configure" #include "confdefs.h" #include <jpeglib.h> configure:2608: checking for socklen_t configure:2622: i386-redhat-linux-gcc -c -O2 -march=i386 -mcpu=i686 -g conftest.c 1>&5 configure:2643: checking for term.h configure:2653: i386-redhat-linux-gcc -E conftest.c >/dev/null 2>conftest.out configure:2649:18: term.h: No such file or directory configure: failed program was: #line 2648 "configure" #include "confdefs.h" #include <term.h> configure:2677: checking for termcap.h configure:2687: i386-redhat-linux-gcc -E conftest.c >/dev/null 2>conftest.out configure:2683:21: termcap.h: No such file or directory configure: failed program was: #line 2682 "configure" #include "confdefs.h" #include <termcap.h> configure:2781: checking for ginac-config |
From: Paul K. <pki...@us...> - 2003-04-03 12:17:13
|
Quentin H. Spencer wrote: > Hello, > > I mentioned on this list a while back that I have created a spec file > for building RPMs of octave-forge. Paul suggested putting it in admin, > which sounds good to me, but now I'm working on autoconfiguration. I > need to determine the octave version and the octave-forge version and > insert them into the spec file. As far as I can tell, this can happen > at one of three different stages: autogen.sh, configure, or the > release.sh script. My natural inclination is to do it in the configure > script, but the release.sh script appears to be the only place where > the octave-forge version is updated for version.h, and it seems like > it would make sense to do it in the same place. Comments? When building from CVS, tag OCTAVE_FORGE_VERSION.m with the date on which you downloaded the CVS snapshot. It doesn't really matter when you tag the spec file, so long as you get the version number from OCTAVE_FORGE_VERSION. Personally, I would create an entry in admin/spec/Makefile to do the tagging so that all the rpm details stay together. To keep version numbering consistent, please break the relevant lines from release.sh into admin/tag_version.sh or some such so that you don't need to run release.sh to build an RPM from a cvs snapshot. Paul Kienzle pki...@us... |
From: Quentin H. S. <qsp...@ie...> - 2003-04-03 05:48:36
|
Hello, I mentioned on this list a while back that I have created a spec file for building RPMs of octave-forge. Paul suggested putting it in admin, which sounds good to me, but now I'm working on autoconfiguration. I need to determine the octave version and the octave-forge version and insert them into the spec file. As far as I can tell, this can happen at one of three different stages: autogen.sh, configure, or the release.sh script. My natural inclination is to do it in the configure script, but the release.sh script appears to be the only place where the octave-forge version is updated for version.h, and it seems like it would make sense to do it in the same place. Comments? Quentin Spencer |
From: Paul K. <pki...@us...> - 2003-04-01 12:25:28
|
ch...@ti... wrote: >Hello > >I(ve git an error compiling the latest forge for octave2.1.44. >Wiatbar compilation fails due to missing tgetnum and tgetstr. >I do have termcap installed. >I use a Mandrake 9.0 distro. > > Please try the CVS version. You can grab configure.add, Makeconf.add and waitbar.cc directly from CVS without downloading the whole package. You will need to go to the octave-forge directory and type ./autogen.sh ./configure .... If this doesn't work, please send a patch to make it work on your system. Or just type make -k so that it doesn't matter if one or two files won't build. Paul Kienzle pki...@us... |
From: =?iso-8859-1?Q?<ch...@ti...> - 2003-04-01 12:10:07
|
Hello=0D=0A=0D=0AI(ve git an error compiling the latest forge for octave2= .1.44.=0D=0AWiatbar compilation fails due to missing tgetnum and tgetstr.= =0D=0AI do have termcap installed.=0D=0AI use a Mandrake 9.0 distro.=0D=0A= =0D=0AAny idea?=0D=0AThanks=0A-------------=0ASPECIAL ADSL =0AL'ADSL =E0 = partir de 15,95 EUR/mois et le modem ADSL offert ? C'est en exclusivit=E9= chez Tiscali !=0APour profiter de cette offre, cliquez ici: http://regis= ter.tiscali.fr/adsl/=0AOffre soumise =E0 conditions.=0A |
From: Paul K. <pki...@ja...> - 2003-03-31 15:42:13
|
Hi all, Anyone have the time to set up and maintain an automated index of octave-forge functions? make_index does most of the work already (though the output is too ugly for words) so it isn't a matter of fixing the html. It's just a matter of figuring out how to set up a cron job on octave.sf.net which: grabs the current tree (presumably with cvs export) runs make_index clears the old html/index directory copies the new octave-forge/index directory The maintenance aspect is grabbing the DOCSTRINGS files for each octave release and putting them someplace where make_index will find them. make_index will need to be modified slightly to use octave/scripts/DOCSTRINGS -- currently it is written to walk the octave/scripts tree. This should be easy enough since it already uses octave/src/DOCSTRINGS, so there is not much to figure out. Thanks in advance, Paul Kienzle pki...@us... |
From: David Bateman<Dav...@mo...> - 2003-03-28 15:49:18
|
Dapr=E8s Paul Kienzle <pki...@ja...> (le 28/03/2003): > On Fri, Mar 28, 2003 at 10:55:57AM +0100, David Bateman wrote: > > With one issue... I changed main/comm/INDEX to include operators (eg > > "+ - =3D Addition and subtraction in a Galois Field.") and all of the > > unimplemented Matlab functions. However, only the functions that are > > either m-files or oct-files are referenced on the webpages. It howeve= r > > seems to have worked for the Signal Processing Toolbox. I imagine it > > is something I have done wrong, but I can't see it... >=20 > I'm not sure what you mean because it works for me now. It does!!! Still doesn't from here.... > It might be that you were trying single character functions by themselv= es. > When it changed from: >=20 > /^\s+(\S+)\s*=3D\s*(\S.*\S)\s*$/ >=20 > to=20 >=20 > /^\s+(\S.*\S)\s*=3D\s*(\S.*\S)\s*$/ >=20 > the following was no longer recognized: >=20 > ! =3D use system("command") >=20 > This has now been fixed. What I was trying to do was allow "fn fn =3D some test" to have two funct= ions referenced by the same text. It works for "make_index" in my directory, a= nd in fact still does, so I thought it would work for the webpages. > BTW, Should the categorical index show the latest release or the > latest CVS? For me its best if its the CVS so I can see any error I make that prevent= ing proper formating rapidly. Is it possible to build the webpages, other tha= n on sourceforge? > There is still a problem with the index in that it does not > handle overloaded functions. For example, >=20 > Galois Fields > ... > size =3D The size of a Galois array In fact "size" isn't an overload, since the generic function can work. Th= e overloaded functions work fine with their specific name. Forinstance "gro= ots" is perfectly referenced. The reason I wanted to include "size", etc, here was to emphasis that the= se functions work in Galois Fields. > does not do anything since the note is ignored if a > function by that name is documented. I now say that the > note is being ignored.=20 This explains some of the problems, but it doesn't explain why "vitdec", etc aren't referenced as "not implemented" since these are the only versions of these functions.... > What we should do is more=20 > complicated. The category specific note should show > up in the category list, but all notes should show up > in the alphabetical list. The current make_index > data structures will not handle this so somebody with > more time than me will have to work on this. I'm the one who wants it, so I imagine this is a hint... > There is also a potential issue with combined notes such as the followi= ng: >=20 > Galois Fields > ... > + - =3D Addition and subtraction in a Galois Field. > * / \ =3D Matrix multiplication and division of Galois arrays. > .* ./ .\ =3D Element by element multiplication and division of Galoi= s arrays. > ** ^ =3D Matrix exponentiation of Galois arrays. > .** .^ =3D Element by element matrix exponentiation of Galois arrays. > ' .' =3D Matrix transpose of Galois arrays. > =3D=3D ~=3D !=3D > >=3D < <=3D =3D Logical operators on Galois array= s. As I said, I made the change to make_index so this works if make_index is run in a directory. > All other type extensions (such as Symbolic and Sparse) will want to us= e > the same sets with the same spacing and ordering within the set since t= he > note is triggered off the entire string. I don't think anything bad wi= ll > happen if the strings are different, so perhaps it won't be a problem. I suggest that the notes are only in the category index and not the alphabetically index. This is the case currently. The advantage is that what you say above becomes a non-problem... D. --=20 David Bateman Dav...@mo... Motorola CRM +33 1 69 35 25 00 (Ph) Espace Technologique, Commune de St Aubin +33 1 69 35 25 01 (Fax) 91193 Gif-Sur-Yvette FRANCE The information contained in this communication has been classified as:=20 [x] General Business Information=20 [ ] Motorola Internal Use Only=20 [ ] Motorola Confidential Proprietary |
From: Paul K. <pki...@ja...> - 2003-03-28 15:15:36
|
On Fri, Mar 28, 2003 at 10:55:57AM +0100, David Bateman wrote: > With one issue... I changed main/comm/INDEX to include operators (eg > "+ - = Addition and subtraction in a Galois Field.") and all of the > unimplemented Matlab functions. However, only the functions that are > either m-files or oct-files are referenced on the webpages. It however > seems to have worked for the Signal Processing Toolbox. I imagine it > is something I have done wrong, but I can't see it... I'm not sure what you mean because it works for me now. It might be that I neglected to do "cvs -q update -dP" before building the index. It might be that you were trying single character functions by themselves. When it changed from: /^\s+(\S+)\s*=\s*(\S.*\S)\s*$/ to /^\s+(\S.*\S)\s*=\s*(\S.*\S)\s*$/ the following was no longer recognized: ! = use system("command") This has now been fixed. BTW, Should the categorical index show the latest release or the latest CVS? There is still a problem with the index in that it does not handle overloaded functions. For example, Galois Fields ... size = The size of a Galois array does not do anything since the note is ignored if a function by that name is documented. I now say that the note is being ignored. What we should do is more complicated. The category specific note should show up in the category list, but all notes should show up in the alphabetical list. The current make_index data structures will not handle this so somebody with more time than me will have to work on this. There is also a potential issue with combined notes such as the following: Galois Fields ... + - = Addition and subtraction in a Galois Field. * / \ = Matrix multiplication and division of Galois arrays. .* ./ .\ = Element by element multiplication and division of Galois arrays. ** ^ = Matrix exponentiation of Galois arrays. .** .^ = Element by element matrix exponentiation of Galois arrays. ' .' = Matrix transpose of Galois arrays. == ~= != > >= < <= = Logical operators on Galois arrays. All other type extensions (such as Symbolic and Sparse) will want to use the same sets with the same spacing and ordering within the set since the note is triggered off the entire string. I don't think anything bad will happen if the strings are different, so perhaps it won't be a problem. Paul Kienzle pki...@us... |
From: David Bateman<Dav...@mo...> - 2003-03-28 09:56:06
|
Dapr=E8s Paul Kienzle <pki...@ja...> (le 27/03/2003): > > Shouldn't that read.. > >=20 > > cat file.texi | makeinfo --fill-column 80 --no-warn --no-validate -= -force --html --ifinfo -o - > file.html >=20 > That seems to do it. Thanks. >=20 > The new version has been posted. With one issue... I changed main/comm/INDEX to include operators (eg "+ - =3D Addition and subtraction in a Galois Field.") and all of the unimplemented Matlab functions. However, only the functions that are either m-files or oct-files are referenced on the webpages. It however seems to have worked for the Signal Processing Toolbox. I imagine it is something I have done wrong, but I can't see it... Cheers D. --=20 David Bateman Dav...@mo... Motorola CRM +33 1 69 35 25 00 (Ph) Espace Technologique, Commune de St Aubin +33 1 69 35 25 01 (Fax) 91193 Gif-Sur-Yvette FRANCE The information contained in this communication has been classified as:=20 [x] General Business Information=20 [ ] Motorola Internal Use Only=20 [ ] Motorola Confidential Proprietary |
From: Paul K. <pki...@ja...> - 2003-03-27 14:35:09
|
On Thu, Mar 27, 2003 at 03:18:20PM +0100, David Bateman wrote: > According to Paul Kienzle <pki...@ja...> (on 03/27/03): > > Yes, I tried to fix it a week or two ago. The problem > > is that the info to html conversion is broken on my machines(?!), > > so no texinfo help is showing. I'm using the following > > (more or less): > > > > cat file.texi | makeinfo --fill-column 80 --no-warn --no-validate --force --html --ifinfo > file.html > > > > If anyone knows a better incantation, I would like to know. > > Shouldn't that read.. > > cat file.texi | makeinfo --fill-column 80 --no-warn --no-validate --force --html --ifinfo -o - > file.html That seems to do it. Thanks. The new version has been posted. > > Also you'll either have to include the macro @seealso, or replace it in your > script make_index... Yes, I was doing that already. Paul Kienzle pki...@us... |
From: David Bateman<Dav...@mo...> - 2003-03-27 14:18:45
|
According to Paul Kienzle <pki...@ja...> (on 03/27/03): > Yes, I tried to fix it a week or two ago. The problem > is that the info to html conversion is broken on my machines(?!), > so no texinfo help is showing. I'm using the following > (more or less): > > cat file.texi | makeinfo --fill-column 80 --no-warn --no-validate --force --html --ifinfo > file.html > > If anyone knows a better incantation, I would like to know. Shouldn't that read.. cat file.texi | makeinfo --fill-column 80 --no-warn --no-validate --force --html --ifinfo -o - > file.html Also you'll either have to include the macro @seealso, or replace it in your script make_index... D. -- David Bateman Dav...@mo... Motorola CRM +33 1 69 35 25 00 (Ph) Espace Technologique, Commune de St Aubin +33 1 69 35 25 01 (Fax) 91193 Gif-Sur-Yvette FRANCE The information contained in this communication has been classified as: [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary |
From: Paul K. <pki...@ja...> - 2003-03-27 14:05:49
|
Yes, I tried to fix it a week or two ago. The problem is that the info to html conversion is broken on my machines(?!), so no texinfo help is showing. I'm using the following (more or less): cat file.texi | makeinfo --fill-column 80 --no-warn --no-validate --force --html --ifinfo > file.html If anyone knows a better incantation, I would like to know. Thanks, Paul Kienzle pki...@us... On Thu, Mar 27, 2003 at 11:53:11AM +0100, David Bateman wrote: > The category index on sourceforge appears to be broken. For instance, > I get the message > > Not Found > The requested URL /index/f/awgn.html was not found on this server. > Apache/1.3.26 Server at octave.sourceforge.net Port 80 > > For many many functions, but funnily not all... |
From: Paul K. <pki...@us...> - 2003-03-07 01:55:17
|
Doug Stewart wrote: > The > http://octave.sourceforge.net/index/ > says > global [language] > not implemented > > But global seems to be working. Very strange. The document is generated automatically from the contents of m-files and cc-files and it seems to be documented in octave. [ dig, dig, dig ] Okay, global is documented as a keyword rather than a function, and doesn't show up in the DOCSTRINGS file. I will add a note describing it in the index. BTW, do you find the index useful? Silly me for building something I don't need myself, because then I wouldn't care if anyone else used it! Please feel free to improve the look and feel of the category index pages. They are generated by the admin/make_index program. Paul Kienzle pki...@us... |
From: Doug S. <da...@sy...> - 2003-03-07 00:36:37
|
The http://octave.sourceforge.net/index/ says global [language] not implemented But global seems to be working. Doug Stewart |
From: Paul K. <pki...@ja...> - 2003-03-05 15:58:18
|
Hi all, I've done a number of changes so that everything will now compile on octave 2.1.36 and up. I tested it on 2.1.36, 2.1.38, 2.1.40 and 2.1.45. The changes were surprisingly minor once I had a handy TRY_MKOCTFILE macro to work with in configure. This gets us to last May. Is it worth cutting a new version for this? There are some issues with m-files. First, there may be gaps because some functions have moved from octave-forge to octave. Interested parties can make an extra/backport directory which is only installed for older versions of octave. Second, there are changes in octave syntax which we cannot support without an m-file preprocessor. Third, there are various bug fixes in octave which we either need to work around or ignore. Until we write [and call!] tests for every m-file, I don't know how big a problem we have. Paul Kienzle pki...@us... |
From: Doug S. <da...@sy...> - 2003-03-05 13:17:47
|
Now does Laplace and SS filters like matlab. Also made the gain positive ( with an abs(...) ). It was negative for odd order filters. Doug Stewart |
From: Doug S. <da...@sy...> - 2003-03-04 14:06:48
|
Now does Laplace and SS filters like matlab. Doug Stewart |
From: Doug S. <da...@sy...> - 2003-03-04 14:06:42
|
Now does Laplace and SS filters like matlab. Doug Stewart |
From: Paul K. <pki...@us...> - 2003-03-02 02:30:44
|
> > >Q1 What we have now: > > I have a heavy version of 2.1.42 (from my website). > This exists in both windows installer version (with nsis packager) > and as cygwin *tar.bz2 packages. > > I was fixing quite a few bugs originally (I'm up to package version 6) > but have not received a bug report for about 3 weeks. > > I propose we put this stuff on octave.sf.net now. > > Sure, its not ideal, but its much better than whats currently on > there, and it buys us time to get the next version right. > Agreed. >>In that case, I would like the user and developer >>versions to be different release files in the same >>release. I know sourceforge will support this since >>I've seen it for example in the tcl file release page: >>http://sourceforge.net/project/showfiles.php?group_id=10894 >> >> > >This is not really a user/developer issue. People who like >cygwin will want octave installed into their cygwin system. >People who don't care about it will want an *.exe to click on. > >I think the different packages should be under different headings. >"octave-forge-cygwin" means nothing to a windows user. >They will not think that packages under that heading are for them. > >I definitely agree that self-install and cygwin versions should share >the same build and files. > I renamed the category to octave-forge-windows. Users can find themselves being developers when they discover an interesting hunk of C code they want to include, so I think it is best to keep the packages together. Nobody starts with octave with the idea that they are going to be developing oct-files for it, but some fools get sucked into it and are trapped forever more ;-) >Q2 What we should have: > > - Best case: A light kernel version with DLD using the > dynamic loaded libstd++.dll > > Advantages: > - compiles same as UNIX - no need to maintain special build. > - each ATLAS in their own DLL - saves space and complexity > - reduces newbie questions. One package does everything. > > Disadvantages: > - will be big unless we can use libstd++.dll > - however, I just tried to build oct-2.1.45 from scratch this > way and ran into linking problems. > I need more details before I can help, other than to say "It worked for me..." > - another future problem is "dllhell" if a future cygwin release > has an incompatible libstd++.dll. > > - I recommend we build octave in /octave or /opt/octave, and > then put libstd++.dll in with the other octave dlls. > That way our libstd++.dll is private to octave. > Agreed. We could still have a problem because different developers are using different versions of cygwin with different versions of stdc++. Will it be enough to include the C++ headers and the libstdc++.dll.a in the developer package? The developer package is starting to sound big: 0.3 Mb libcruft.dll.a 2.3 Mb liboctave.dll.a 3.0 Mb liboctinterp.dll.a 1.0 Mb include/octave 1.5 Mb libstdc++.dll.a 2.0 Mb include/c++ ?.? Mb include/lapack ?.? Mb include/lapack.dll.a 0.0 Mb bin/mkoctfile, etc. I'm assuming the developer package requires the user package to be installed first, otherwise we have to add on that. Fortunately it compresses well. The files listed above (sans lapack) compress to only 0.6 Mb! I'm not sure the problem is any less if the developer package is statically linked to libstdc++. > - The other options (heavy, semi-heavy, big ...) all have problems. > I recommend we try to get the best case working, and not look > at the other options until this proves impossible. > That's my feeling, unless someone has a good reason not to use DLLs. Also, as DLLs, I think it will be easier to embed octave directly in tcl/perl/R ... >>I've tested the light kernel option. It works fine except >>that the fork problem on recent cygwin for Win 9x is >>exacerbated (not only is it slow, it also pops up error >>messages for each loaded oct-file). The solution is to >>purge the octave code of fork, but I haven't had a >>chance to do so yet. >> >> > >My opinion on 9x support is not to try very hard. > I have no choice. Another thing is that removing fork gets us one step closer to a MinGW version. With the revised (ugly) signal handling, Ctrl-C can be made to work, at least in conforming code. Foreign code such as lapack will still need trickery. >I say we put >up the 2.1.42 heavy option now (which should work fine on 9x) and then >move to something with dynamic linking in future. > Okay. Shall I leave the -2.1.3x as is, or should I rename them to -2.1.3x-developer? |