[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #43164] Unable to build packages due to anothe

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #43164] Unable to build packages due to another installation of GCC or MinGW in PATH variable
Date: Sun, 07 Sep 2014 12:09:09 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 Iceape/2.22

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   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:


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

(also attached)

(file #32041)

Additional Item Attachment:

File name: Octave.bat                     Size:0 KB


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]