[Top][All Lists]

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

Re: building octave 2.9.5 on Tiger

From: Joe Koski
Subject: Re: building octave 2.9.5 on Tiger
Date: Sat, 24 Jun 2006 12:31:00 -0600
User-agent: Microsoft-Entourage/

on 6/24/06 10:59 AM, Daniel Oberhoff at address@hidden wrote:

> I have 2.9.6. I only started using it because I could not get 2.1.7
> to cleanly configure and install (but maybe I did something wrong and
> should try again). What are those files anyhow? Because to me the
> installation seems a little slim, there is only the octfiles, a
> PKG_ADD file and m files besides the binaries. No startup scripts or
> such whatsoever.
> Daniel


If you just want a working copy of octave-2.1.73 with octave-forge for
normal work, go to and install the binaries from there.
The installation is relatively easy with the instructions given there.

The only disadvantage I can think of for using the HPC approach is that the
HPC binaries were not built for the dependencies on your particular machine.
Some obscure things (like reading some image formats) may not work, but the
day-to-day stuff works fine.


> Am Jun 24, 2006 um 6:38 PM schrieb John W. Eaton:
>> | I remember seeing a similar problem when I was messing around
>> with 2.95+
>> | on my PowerMac.  I was using the fink compiler, so it isn't an
>> artifact
>> | of using the Apple compiler.  In my case, it was a problem of
>> startup
>> | files not being run properly.  This was a while ago, so I don't
>> remember
>> | very well, but it seems like whatever scripts went through and
>> aliased
>> | function names to OCT files were messed up.  This made it so min,
>> max,
>> | and gnuplot stuff didn't work.  It may have been a problem of me
>> having
>> | 2 sets of startup files; one in /usr/local/* for an older CVS
>> version
>> | and one in /opt/* for the 295+ CVS version and for some reason it
>> was
>> | finding the older startup scripts.
>> Yes, I think there was a bug in one of the Makefiles in 2.9.5 which
>> caused the install target to miss a few files.  I don't remember the
>> details, but this problem is fixed in 2.9.6, which at this point is
>> what I would recommend you try instead of 2.9.5 if you want to work
>> with Octave 2.9.x.
>> jwe
> _______________________________________________
> Help-octave mailing list
> address@hidden

reply via email to

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