Editing Octave and separate toolchain

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{Warning|This page is outdated (October 2019).  For a simpler approach on building GNU Octave using a separate toolchain, see [[MXE]].}}
+
{{Warning|This page is outdated (October 2019).  For a more active approach on building GNU Octave using a separate toolchain, see [[MXE]].}}
  
 
Building of octave together with a separate toolchain (custom built gcc/binutils/...).
 
Building of octave together with a separate toolchain (custom built gcc/binutils/...).
  
 
This is required mainly when the base linux distribution ships too old a version of gcc.
 
This is required mainly when the base linux distribution ships too old a version of gcc.
Unexperienced users should upgrade their distribution, though. Or use [[MXE]].
+
Unexperienced users should upgrade their distribution, though.
  
 
The main build directory will be called {{Path|/usr/local/build}}.  
 
The main build directory will be called {{Path|/usr/local/build}}.  

Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)