From: Rafael L. <rla...@us...> - 2005-04-27 10:25:16
|
[Cc: to the octave-dev mailing list. Please respect the M-F-T header.] * Kuhn, Jonathan <jon...@me...> [2005-04-26 15:58]: > I get the following error when I try to run delaunay in octave. > > >> x = [1:15]; > >> y = [1:15]; > >> [x,y]=meshgrid(x,y); > >> x=reshape(x,15*15,1); > >> y=reshape(y,15*15,1); > >> tri=delaunay(x,y) > error: `delaunayn' undefined near line 51 column 13 > error: evaluating assignment expression near line 51, column 11 > error: evaluating if command near line 50, column 5 > error: evaluating if command near line 49, column 3 > error: called from `delaunay' in file `/usr/share/octave/2.1.49/site/m/octave-fo > rge/geometry/delaunay.m' > error: evaluating assignment expression near line 42, column 4 This is a problem with your installation of the octave-forge package and has nothing to do with Octave itself. The file delaunayn.oct is probably lacking in your system or is in a wrong place. -- Rafael |
From: Rafael L. <rla...@us...> - 2005-04-28 10:27:57
|
[Please, respect the M-T-F header. Thanks.] * Kuhn, Jonathan <jon...@me...> [2005-04-27 08:35]: > Thanks! I updated to 2.1.69 and delaunay is working, but now it can not > find the function 'griddata'. I have here: $ octave-config --version 2.1.69 $ echo "which griddata" | octave -q -f griddata is the user-defined function from the file /usr/share/octave/site/m/octave-forge/geometry/griddata.m -- Rafael |
From: Dmitri A. S. <das...@gm...> - 2005-04-27 13:49:58
|
Rafael Laboissiere wrote: >>error: `delaunayn' undefined near line 51 column 13 >>error: evaluating assignment expression near line 51, column 11 >>error: evaluating if command near line 50, column 5 >>error: evaluating if command near line 49, column 3 >>error: called from `delaunay' in file `/usr/share/octave/2.1.49/site/m/octave-fo >>rge/geometry/delaunay.m' >>error: evaluating assignment expression near line 42, column 4 > > > This is a problem with your installation of the octave-forge package and > has nothing to do with Octave itself. The file delaunayn.oct is probably > lacking in your system or is in a wrong place. > I noticed that "make install" in octave-forge would install delaunay.m (and related) even though qhull is not present and delaunayn.oct has not being built. Perhaps this is a bug in the octave-forge configure script? Sincerely, Dmitri. -- |
From: Rafael L. <rla...@us...> - 2005-04-28 09:15:43
|
* Dmitri A. Sergatskov <das...@gm...> [2005-04-27 07:49]: > I noticed that "make install" in octave-forge would install delaunay.m > (and related) even though qhull is not present and delaunayn.oct has > not being built. Perhaps this is a bug in the octave-forge configure > script? Yes, it seems to be a bug. Unfortunately, I am not very used to the octave-forge configure/Makefile scheme and I would prefer that someone else review this issue. -- Rafael |
From: Paul K. <pki...@us...> - 2005-05-30 03:07:11
|
On Apr 28, 2005, at 5:15 AM, Rafael Laboissiere wrote: > * Dmitri A. Sergatskov <das...@gm...> [2005-04-27 07:49]: > >> I noticed that "make install" in octave-forge would install delaunay.m >> (and related) even though qhull is not present and delaunayn.oct has >> not being built. Perhaps this is a bug in the octave-forge configure >> script? > > Yes, it seems to be a bug. Unfortunately, I am not very used to the > octave-forge configure/Makefile scheme and I would prefer that someone > else review this issue. Install is mostly handled by main/Makefile, which walks through every subdirectory without a NOINSTALL file and runs octinst.sh on it. This installs every oct-file and m-file. The quick hack is to figure out how to make ./configure touch or remove main/geometry/NOINSTALL depending on whether qhull is present. You can't do it from main/geometry/Makefile since this will not be used if main/geometry/NOINSTALL is present. This isn't a very good solution. Perhaps it is time to rethink the idea of automatically installing every m-file and oct-file in a directory, and instead go back to explicitly listing the files which need to be installed. In the meantime, I'm inclined to live with a non-working delaunay.m installed when qhull is not present. - Paul |