[Octave-bug-tracker] [bug #40381] MXE / MinGW - setenv does not work correctly

[Philip Nienhuis]

Follow-up Comment #23, bug #40381 (project octave):

@ John (JWE): your fix works OK for me; the /bin subdir is added to the PATH
now when executing octave.exe directly, and octave-gui.exe is started. On my
WinXP box:

>> strsplit (getenv ("PATH"), pathsep)
ans =
{
  [1,1] = C:\WINDOWS\system32
  [1,2] = C:\WINDOWS
  [1,3] = C:\WINDOWS\System32\Wbem
  [1,4] = C:\Programs\TortoiseSVN\bin
  [1,5] = C:\Programs\gs\gs9.04\bin
  [1,6] = C:\Programs\QuickTime\QTSystem\
  [1,7] = C:\Programs\Mercurial
  [1,8] = X:\Octave\octave-2013-10-29-19-15\bin
  [1,9] = X:\Octave\octave-2013-10-29-19-15\notepad++
  [1,10] =
X:\Octave\octave-2013-10-29-19-15\libexec\octave\3.7.7+\site\exec\i686-pc-mingw32
  [1,11] =
X:\Octave\octave-2013-10-29-19-15\libexec\octave\api-v48+\site\exec\i686-pc-mingw32
  [1,12] =
X:\Octave\octave-2013-10-29-19-15\libexec\octave\site\exec\i686-pc-mingw32
  [1,13] =
X:\Octave\octave-2013-10-29-19-15\libexec\octave\3.7.7+\exec\i686-pc-mingw32
  [1,14] = X:\Octave\octave-2013-10-29-19-15\bin
}
>>


/bin has been added twice, but that isn't in the way.

Is it really necessary to add the libexec/.../i686-pc-mingw32 subdirs to the
PATH? (not that it is harmful in any way) - I see no difference with the
current situation and the previous one where I only had /bin added (by calling
Octave from a batch file that first added (only) /bin to the PATH).

Do we leave it to John Donoghue to close this bug?


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?40381>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/