Thu 20 Jan 2011 11:39:43 AM UTC, comment #9:
No need to re-open, but I wanted to mention that I have some info from Lukas Reichlin <lukas.reichlin@swissonline.ch> on how to build using MacPorts. I've been meaning to summarize and post to the list for review, but haven't had the time yet.
|
Fri 24 Dec 2010 10:45:27 PM UTC, comment #8:
When I've had problems with tests failing, I've tried changing the level of optimization. Sometimes I got different results with Apple's gcc than had been reported by those using gcc on Linux, mingw, etc. However, at the present time both "-O2" and "-O0" result in one test failure.
Thus, I think changing the optimization level to "-O2" is a good idea.
I also like the idea of asking a MacPorts user to add to the Readme.MacOS file.
Michael Godfrey prefers to avoid the package managers (Fink & MacPorts) and has posted his instructions for building Octave to the list.
If you'd like me to take care of any of these, please let me know.
|
Fri 24 Dec 2010 03:26:02 PM UTC, comment #7:
Version 3 of the instructions looked good so I checked in README.MacOS.
One question is about the optimization flags. The instructions have
but this always leads to one of the sqrt tests failing with gcc. I need to use '-O1' or above in order for gcc to compile the source correctly. Shouldn't we be recommending '-O1' or '-O2'?
Second, there were two sections marked TODO. Should we poll on the octave-maintainers list for another mac user who uses the Macport distribution who could write that section?
|
Tue 21 Dec 2010 12:14:08 AM UTC, comment #6:
My understanding it that perl comes standard with MacOS (its built on BSD Unix), and that all Fink installations include texinfo, and tetex. However, as tetex is no longer maintained the Fink team has been wanting to move away from tetex and toward TeX-Live. Perhaps it is best to mention that texinfo and tetex are default packages?
I've attached v3.
(file #22250)
|
Mon 20 Dec 2010 11:06:29 PM UTC, comment #5:
I reviewed your file and made a few language, not content, changes. I've re-posted the new file to the Bug Tracker.
I have two questions. In the list of dependencies there is no mention of perl or Texinfo. Are these already installed by default by Xcode and therefore don't need mentioning?
The instructions are for OSX 10.6, but in the environment variables there is a setting
Is that right?
(file #22249)
|
Sat 18 Dec 2010 09:19:44 PM UTC, comment #4:
I'm not sure just how much to include. I've included everything needed to build using the gcc which accompanies Apple's developer's tools (Xcode).
I haven't pushed yet. If it looks ok, I can do so.
(file #22229)
|
Sat 18 Dec 2010 04:32:08 AM UTC, comment #3:
I added a mostly blank file, README.MacOS, to the top-level directory (http://hg.savannah.gnu.org/hgweb/octave/rev/fba7b5538b18). Hopefully you can fill it in with your instructions. The file README.MSVC seems like a good template for how the file might be organized.
|
Sat 18 Dec 2010 02:32:51 AM UTC, comment #2:
The section on building with --enable-64 in doc/interpreter/install.txi contains a list of dependencies and tips for building them for 64-bit indexing. We should probably also have a separate list of just the dependencies and perhaps some tips about how they can be installed various systems.
|
Sat 18 Dec 2010 02:24:31 AM UTC, comment #1:
I like the idea. From my experience, building on MacOS X depends upon the version of the OS and how the dependencies are satisfied.
I recommend the README.MacOS (?) is written for Snow Leopard (10.6.x).
For MacOS the dependencies can be satisfied manually, via MacPorts, or via Fink. However, the most important detail is that all libraries be built with the same gcc compiler as used to build Octave.
Are the dependencies listed elsewhere?
|
Fri 17 Dec 2010 05:45:38 PM UTC, original submission:
The intricacies of building and installing Octave on Mac OSX systems are complicated enough to warrant a set of instructions. The top-level directory of Octave contains various files which deal with special instructions for specific architectures such as README.Cray or INSTALL.Windows.
Could someone who has had success on the OSX platform write up the necessary steps?
|