#1572 OSX build problem with 5.17.1


I am tryiing to builld 5.17.1 on OSX 10.5.6.
I can get the command lin version to work with CMUCL.
With 'sudo make install' I get

Making install in info
pattern=`printf "\r$"` ; \ bad_files=`find . -name '*.texi' -print | xargs grep -E -l -e "$pattern"` ; \ [ -z "$bad_files" ] || ( echo "WARNING: The following files have DOS-style EOLs: $bad_files" ; \ echo "Run /doc/info/fix_crlf to fix the problem." )
pattern=`printf "\t"` ; \ bad_files=`find . -name '*.texi' -print | xargs grep -E -l -e "$pattern"` ; \ [ -z "$bad_files" ] || ( echo "WARNING: The following files have unexpanded Tabs: $bad_files" ; \ echo "Run /doc/info/fix_tab to fix the problem." )
make[4]: Nothing to be done for `install-exec-am'.
sh extract_categories.sh maxima
sh: extract_categories.sh: No such file or directory
make[4]: *** [maxima.html] Error 127
make[3]: *** [install-am] Error 2
make[2]: *** [install-recursive] Error 1
make[1]: *** [install-recursive] Error 1
make: *** [install-recursive] Error 1

xmaxima can be started, but double clicking the commands to be run does not produce results.


  • Raymond Toy

    Raymond Toy - 2009-01-25

    I didn't try 5.17.1, but the CVS version installs ok for me on OSX and CMUCL.

    I do get lots of notes about unknown previous node when building the documentation.

  • Robert Dodier

    Robert Dodier - 2009-01-27

    I'm guessing that you are attempting to build Maxima from a tar ball. If not, please say so.

    The Maxima tar ball is supposed to contain the generated documentation (.info and .html files). What does the following show:

    tar tvzf maxima-5.17.1.tar.gz | grep 'maxima\.\(info\|html\)$'

    The intent is to detect maxima.info and maxima.html at the end of a line. You might need to adjust the regular expression.

    If your tarball does not contain maxima.info or maxima.html files, from where did you get it? If you did not get it from Sourceforge, you might obtain the tarball from the Maxima download page and try again.

    If your tarball does contain the generated documentation, make should not be trying to build it. If make is trying to build existing files, come back and leave another comment and we'll go from there.

  • Erich Neuwirth

    Erich Neuwirth - 2009-01-27

    Requested grep output

  • Erich Neuwirth

    Erich Neuwirth - 2009-01-27

    I did use the latest tarball. Attached is the output of the grep as you requested.
    The files were already untarred, so I just grepped in the untarred directory.
    I also checked out the current version from cvs, and I have the same problem.
    Maxima itself works, but in xmaxima clicking the links does no work.
    In wxMaxima (I managed to build it with the instructions by Stuart Schmitt on
    When I try to start maxima I get Maxima process terminated.

    File Added: grep.out

  • Erich Neuwirth

    Erich Neuwirth - 2009-01-27

    More info:
    I managed to get wxMaxima to run now. Compling from the tarball produced a running version. Compiling from the cvs download seemed to compile, but wxMaxima told me
    Maxima process terminated.
    xmaxima still does not work. I see (%i1), but on enter and on Shft-Enter nothing happens, and clicking on the editable expressens in the lower window does not do anything either.
    But I am happy with a running wxMaxima in any case.

  • Robert Dodier

    Robert Dodier - 2009-02-25

    > I did use the latest tarball. Attached is the output of the grep as you

    The grep output is something different. I'm attempting to determine whether the info (texinfo output) and html files are present in the tarball. Can you please run the tar/grep command as it was shown. Here it is for reference.

    tar tvzf maxima-5.17.1.tar.gz | grep 'maxima\.\(info\|html\)$'

  • Dieter Kaiser

    Dieter Kaiser - 2009-12-16

    This bug report seems to be out of date. There is no response to the last posting. Now we have Maxima 5.20.
    Setting the status to pending and the resolution to "out of date".
    Dieter Kaiser

  • Dieter Kaiser

    Dieter Kaiser - 2009-12-16
    • status: open --> pending
  • SourceForge Robot

    • status: pending --> closed
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks