error building Octave
and.damore at macports.org
Tue May 11 23:45:54 PDT 2010
On Wed, May 12, 2010 at 3:28 AM, Liam Groener <liamg at mac.com> wrote:
> I tried to build Octave 3.2.4 on an Mac OS X 10.6.3 machine. As I had Octave 3.2.3 already installed, I uninstalled it before attempting to install 3.2.4.
Macports would have done it on its own while running "upgrade" action.
You could also have only deactivated it, "just in case".
> ./octave.aux:4743: TeX capacity exceeded, sorry [save size=5000].
> /opt/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
Here is the problem, while building octave pdfetex exits with error
and port can't complete the build phase.
A quick search shows these tentative fix instructions:
sudo vi /usr/share/texmf/web2c/texmf.cnf
Replace save_size with a larger value, say 50000
where /usr/ will probably be /opt/local or whatever the macports
prefix is (I don't have pdfetex on my system atm).
Can you paste the output of "port installed texinfo" ?
> Before reporting a bug, first run the command again with the -d flag to get complete output.
> iMac-4718:~ liamg$ octave -d
Notice that the output says "again" so it refers to a command you
already ran, thus not "octave" but "port", i.e. "sudo port -d install
> /Users/liamg/bin/octave: line 3: /opt/local/bin/octave-3.2.3: No such file or directory
> iMac-4718:~ liamg$ sudo install octave -d
> install: octave: Inappropriate file type or format
"install" is a tool to install files, chances are there is no "octave"
file in the working directory and even if there were one it wouldn't
make much sense anyway. Probably you wanted "sudo port install"
Remember that you can perform a clean action "sudo port clean octave"
(no need to use "-d" with clean) to clean a broken previous build.
> My Unix is weak and I don't know what to do next?
Very Jedi-ish it is, hmmm.
More information about the macports-users