Re: README.MacOS

[Lukas Reichlin]

On 27.01.2011, at 03:02, Ben Abbott wrote:

> On Jan 24, 2011, at 9:30 PM, Ben Abbott wrote:
> 
>> On Jan 24, 2011, at 7:52 AM, Ben Abbott wrote:
>> 
>>> On Jan 24, 2011, at 5:56 AM, Jarno Rajahalme wrote:
>>>> 
>>>> On Jan 24, 2011, at 9:51 , ext John W. Eaton wrote:
>>>> 
>>>>> On 23-Jan-2011, Ben Abbott wrote:
>>>>> 
>>>>> | I've edited the README.MacOS file to include instructions on using 
>>>>> MacPorts.
>>>>> | 
>>>>> | I'm not a MacPorts user so I may have some things wrong.
>>>>> | 
>>>>> | Corrections and/or constructive critique would be appreciated.
>>>>> 
>>>>> | 1. General Users
>>>>> | ================
>>>>> | 
>>>>> | A MacOS bundle is available from sourceforge.
>>>>> | 
>>>>> |   http://octave.sourceforge.net/index.html
>>>>> | 
>>>>> | There are also Octave packages available from both Fink and MacPorts.  
>>>>> Each
>>>>> | of these package managers handle the details of compiling Octave from 
>>>>> source.
>>>>> | 
>>>>> |   http://www.finkproject.com
>>>>> |   http://www.macports.org/
>>>>> 
>>>>> Users might also want to build from source for various reasons.  They
>>>>> will probably want to build using a stable release rather than using
>>>>> the sources from the Mercurial archive.  So you might rename this
>>>>> first section "Easy to install Binary Releases" (or similar) and the
>>>>> section for Developers could be renamed "Building from Source" and
>>>>> then explain where and how to get the sources from Mercurial (you
>>>>> could just point to the instructions on savannah) and also that stable
>>>>> releases are availble from ftp.gnu.org in the directory
>>>>> pub/gnu/octave.  Then I think the only difference in the directions
>>>>> would be that once you've got the sources you should skip the
>>>>> autogen.sh step if you are building from sources downloaded in a tar
>>>>> file.
>>>>> 
>>>>> jwe
>>>> 
>>>> I have been building Octave from sources on OSX using GCC 4.5. To avoid 
>>>> crashes LDFLAGS needs to have the newer libstdc++ as the first file to be 
>>>> linked with, like:
>>>> 
>>>> export LDFLAGS="/opt/local/lib/gcc45/libstdc++.6.dylib"
>>>> 
>>>> (Above before ./configure)
>>>> 
>>>> Without this Octave segfaults when compiled with newer-than-Apple GCC.
>>>> 
>>>> Also, Apple blas (vecLib) does not work with 64-bit gfortran (4.2, 4.3, 
>>>> 4.4, nor 4.5). Complex functions obviously fail (and segment fault) 
>>>> without -ff2c option, but then other non-complex routines return incorrect 
>>>> answers when -ff2c is enabled, so that configure fails. So with 64-bit OSX 
>>>> you pretty much have to use atlas and/or lapack.
>>>> 
>>>> Would information like this be of interest in README.MacOS?
>>>> 
>>>> Jarno
>>> 
>>> I'll make these changes and post the result later today.
>>> 
>>> Thanks
>>> Ben
>> 
>> A modified version is attached.
>> 
>> Ben
>> 
>> <README.MacOS>
> 
> I've pushed a modified version of README.MacOS
> 
>       http://hg.savannah.gnu.org/hgweb/octave/rev/2ba904181687
> 
> The section on describing "Manual Package Management" is still empty. I was 
> pleased to see the several emails exchanged on this subject. Unfortunately, I 
> have been unable to keep up.
> 
> I encourage those who are building without Fink and MacPorts to propose 
> instructions that can be inserted into the current version. Changesets are 
> preferred, but I am happy to handle a diff as well.
> 
> We may wish to include 32bit and 64bit sections.
> 
> Thanks
> Ben

Follow-up comment:

   2.220
 +    sudo port uninstall octave-devel

   2.221
 +

   2.222
 +This will remove Octave and leave its dependencies in place. Now Octave may be


Probably the command
sudo port deactivate octave-devel
is better than the "uninstall" one since you can activate the port again by 
typing
sudo port activate octave-devel
without a rebuild. It is possible to have several inactive versions of a port 
at the same time.

Lukas