From help-octave-request at bevo dot che dot wisc dot edu Tue Jun 23 00:28:15 1998 Subject: win95 install From: "John W. Eaton" To: Erich Neuwirth Cc: help-octave at bevo dot che dot wisc dot edu Date: Tue, 23 Jun 1998 00:26:51 -0500 (CDT) On 7-Jun-1998, Erich Neuwirth wrote: | i am experiencing problems when installing the gnuwin32 version | of octave 2.0.13 | | i followed the instructions and | did a setup to the default directories. | | the binary now works. | but it cannot find the m files. | | here is what i get for LOADPATH | | octave.exe:1> LOADPATH | LOADPATH = | .:/octave/libexec/octave/site/oct/i386-pc-cygwin32//:/octave/share/oc | tave/site/m//:/octave/libexec/octave/2.0.13/oct/i386-pc-cygwin32//:/octave/share | /octave/2.0.13/m// | octave.exe:2> | | | additionally, during the installation | | xargs crashed once, | but the installation continued. That sounds like a bug. Can you please send a more detailed bug report to bug-octave at bevo dot che dot wisc dot edu? If it really is a problem with xargs on gnu-win32 systems, and not a problem with the way the Octave installation scripts call xargs, can you please submit a bug report to the gnu-win32 project? | final question: | | | bin contained | octave.bin | | but NOT octave.exe | | is this the way of working. | | when i renamed octave.bin to octave.exe | i could start it. | | what am i supposed to do about this? The bin directory should have also contained a shell script called `octave' that you can run from a bash shell window. If not, renaming the binary should work fine as long as you installed Octave in the default directory tree (i.e., /octave/...). Otherwise, some environment variables will need to be set in order for Octave to run correctly. jwe