[Octave-bug-tracker] [bug #43164] Unable to build packages due to another installation of GCC or MinGW in PATH variable

[Philip Nienhuis]

Follow-up Comment #1, bug #43164 (project octave):

Yeah I'm sorry but this really looks to be caused by your own way of setting
up things.
You'd better set environment variables through batch filea, rather than put it
all in a global environment valid for all user programs.

That said, we really need a batch file to start Octave on MinGW, to help clean
up the Windows PATH from all junk that users and user programs (on purpose or
not, with or without their knowledge) have put there and that clobbers up
Octave's execution.

I use the following (to be put in Octave's installation subdir):

@echo off
Rem   Find Octave's install directory through cmd.exe variables.
Rem   This batch file should reside in Octaves installation subdir!
Rem
Rem   This trick finds the location where the batch file resides.
Rem   Note: the result ends with a backslash
set OCT_HOME=%~dp0

Rem   Set up PATH. Make sure the Octave-version-specific subdir
Rem   comes first. Use system environment variables for the
Rem   Windows system dirs.
Rem   Ghostscript is still an issue, I've left my setup for it
Rem   in the line below:

set 
PATH=%OCT_HOME%bin;%windir%\system32;%windir%;%windir%\system32\wbem;%OCT_HOME%gs\gs9.14\bin

Rem   Start Octave (this detaches octave-gui and immediately
Rem   returns):
start octave-gui.exe
Rem  or
REM start octave-cli.exe

Rem   Close the batch file's cmd.exe window
exit

(also attached)



(file #32041)
    _______________________________________________________

Additional Item Attachment:

File name: Octave.bat                     Size:0 KB


    _______________________________________________________

Reply to this item at:

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

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