X-Spam-Check-By: sourceware.org
Message-ID: <20051201175030.88155.qmail@web51515.mail.yahoo.com>
Date: Thu, 1 Dec 2005 09:50:30 -0800 (PST)
From: "James R. Phillips" <antiskid56-cygwin AT yahoo DOT com>
Reply-To: antiskid56-cygwin AT yahoo DOT com
Subject: Issues Upgrading Octave and Octave-Forge
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

For those that are upgrading octave and octave-forge to the newest releases, be
certain that you are not using octave at the time of the upgrade, otherwise the
installation may not update files that are in use, resulting in a partial
installation.

If you get a 2.1.71 version message upon loading 2.1.72, this has happened to
you.  Quit all octave sessions, and reinstall the upgrades.

Note also that to compile .oct files, you need to use gcc 3.3.3.  Both octave
and octave-forge are compiled using this version.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/