maxima does not build on 64-bit OSX 10.6.8 - logs?

[Dima Pasechnik]

In another thread, it was mentioned that maxima does not build on 64-bit OSX 10.6.8.

How does one see the log of such a build?

Is there any way?

As all one sees on OSX by default is the following:

Now building Maxima; this takes a few minutes.

Since we're on MacOS X and there is a very weird

bug with buffered output while building Maxima,

you will not be able to see the output of the build

as it occurs.  Don't worry, the build process does

not hang.

Thanks,

Dima

[François Bissey]

Stupid question: Is the file spkg/log/maxima-5.xxxx.log available?

Francois

[Dima Pasechnik]

the attachment here:

https://groups.google.com/d/msg/sage-devel/oYuthqwvtuw/L1L2FFpWeFUJ

 

Francois

[Francois Bissey]

ok. so it has nothing in it. As far as I understand the buffering problem is
somewhat specific of the sage building process. I don't have it in a Gentoo
prefix on OS X.

So I suggest starting a sage shell (maxima should be built after sage) and try
to build maxima manually. Go to spkg/build/maxima-5.26.0.p0/src and then
'make' and see what happens.

Francois

[kfiz]

Hi Francois,

when opening a sage-shell I get a huge traceback: 

Doro-Roses-MacBook-Pro:sage-5.1 louis$ ./sage

----------------------------------------------------------------------

| Sage Version 5.1, Release Date: 2012-07-09                         |

| Type "notebook()" for the browser-based notebook interface.        |

| Type "help()" for help.                                            |

----------------------------------------------------------------------

---------------------------------------------------------------------------

ImportError                               Traceback (most recent call last)

/Applications/sage-5.1/local/bin/<string> in <module>()

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/misc/preparser_ipython.py in <module>()

      6 ###########################################################################

      7 

----> 8 import sage.misc.interpreter

      9 

     10 import preparser

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/misc/interpreter.py in <module>()

    103 

    104 import os

--> 105 import log

    106 import re

    107 

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/misc/log.py in <module>()

     63 

     64 import interpreter

---> 65 import latex

     66 import misc

     67 

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/misc/latex.py in <module>()

     55 import types

     56 

---> 57 from misc import tmp_dir, graphics_filename

     58 import sage_eval

     59 from sage.misc.sage_ostools import have_program

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/misc/misc.py in <module>()

   2161     return "0"*(size-len(str(s))) + str(s)

   2162 

-> 2163 import sage.server.support

   2164 

   2165 def embedded():

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/server/support.py in <module>()

     17 import sage.misc.pager

     18 

---> 19 import sage.misc.sagedoc as sagedoc

     20 import sage.misc.sageinspect as sageinspect

     21 

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/misc/sagedoc.py in <module>()

     38 from sage.misc.viewer import browser

     39 from sage.misc.misc import SAGE_DOC, tmp_dir

---> 40 from sagenb.misc.sphinxify import sphinxify

     41 import sage.version

     42 

ImportError: No module named sagenb.misc.sphinxify

WARNING: Failure executing code: 'import sage.misc.preparser_ipython;  sage.misc.preparser_ipython.magma_colon_equals=True'

---------------------------------------------------------------------------

ImportError                               Traceback (most recent call last)

/Applications/sage-5.1/local/lib/python2.7/site-packages/IPython/ipmaker.pyc in force_import(modname, force_reload)

     61         reload(sys.modules[modname])

     62     else:

---> 63         __import__(modname)

     64         

     65 

/Applications/sage-5.1/local/bin/ipy_profile_sage.py in <module>()

      1 import os

      2 if 'SAGE_CLEAN' not in os.environ:

----> 3     import sage.misc.misc

      4     from sage.misc.interpreter import preparser, _ip

      5     preparser(True)

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/misc/misc.py in <module>()

   2161     return "0"*(size-len(str(s))) + str(s)

   2162 

-> 2163 import sage.server.support

   2164 

   2165 def embedded():

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/server/support.py in <module>()

     17 import sage.misc.pager

     18 

---> 19 import sage.misc.sagedoc as sagedoc

     20 import sage.misc.sageinspect as sageinspect

     21 

/Applications/sage-5.1/local/lib/python2.7/site-packages/sage/misc/sagedoc.py in <module>()

     38 from sage.misc.viewer import browser

     39 from sage.misc.misc import SAGE_DOC, tmp_dir

---> 40 from sagenb.misc.sphinxify import sphinxify

     41 import sage.version

     42 

ImportError: No module named sagenb.misc.sphinxify

Error importing ipy_profile_sage - perhaps you should run %upgrade?

WARNING: Loading of ipy_profile_sage failed.

<ERROR: name 'sage_prompt' is not defined>

trying to build maxima manually from terminal doesn't work either. I get the following:

Doro-Roses-MacBook-Pro:src louis$ make

Making all in admin

make[1]: Nothing to be done for `all'.

Making all in src

test -d binary-ecl || mkdir binary-ecl

ecl -norc -eval '(progn (load "../lisp-utils/defsystem.lisp") (load "../lisp-utils/make-depends.lisp") (funcall (intern "CREATE-DEPENDENCY-FILE" :mk) "binary-ecl/maxima" "ecl-depends.mk") (quit))'

make[1]: ecl: No such file or directory

make[1]: *** [ecl-depends.mk] Error 1

make: *** [all-recursive] Error 1

...or am I doing something wrong here?

Doro

 

[Francois Bissey]

> y in <module>()
> 38 from sage.misc.viewer import browser
> 39 from sage.misc.misc import SAGE_DOC, tmp_dir
> ---> 40 from sagenb.misc.sphinxify import sphinxify
> 41 import sage.version
> 42
>
> ImportError: No module named sagenb.misc.sphinxify
> Error importing ipy_profile_sage - perhaps you should run %upgrade?
> WARNING: Loading of ipy_profile_sage failed.
>
> <ERROR: name 'sage_prompt' is not defined>
>
>
>
>
> trying to build maxima manually from terminal doesn't work either. I get
> the following:
>
> Doro-Roses-MacBook-Pro:src louis$ make
> Making all in admin
> make[1]: Nothing to be done for `all'.
> Making all in src
> test -d binary-ecl || mkdir binary-ecl
> ecl -norc -eval '(progn (load "../lisp-utils/defsystem.lisp") (load
> "../lisp-utils/make-depends.lisp") (funcall (intern
> "CREATE-DEPENDENCY-FILE" :mk) "binary-ecl/maxima" "ecl-depends.mk") (quit))'
> make[1]: ecl: No such file or directory
> make[1]: *** [ecl-depends.mk] Error 1
> make: *** [all-recursive] Error 1
>
> ...or am I doing something wrong here?
>

I am really sorry Doro. I meant for you to do start a sage shell with
./sage -sh
This loads the variables used by sage in a shell. what you would
have got with "./sage" should be called the sage prompt.
Because the environment was not set the make command was bound to fail.

So please try again after ./sage -sh

Francois

[kfiz]

No problem. I'm rather unexperienced with operations in the shell, so I probably wouldn't have known the difference. ;-)

So here is what happens when I try to 'make' maxima in a sage-shell:

(sage-sh) louis@Doro-Roses-MacBook-Pro:src$ make

Making all in admin

make[1]: Nothing to be done for `all'.

Making all in src

test -d binary-ecl || mkdir binary-ecl

ecl -norc -eval '(progn (load "../lisp-utils/defsystem.lisp") (load "../lisp-utils/make-depends.lisp") (funcall (intern "CREATE-DEPENDENCY-FILE" :mk) "binary-ecl/maxima" "ecl-depends.mk") (quit))'

;;; Loading "/Applications/sage-5.1/spkg/build/maxima-5.26.0.p0/src/src/../lisp-utils/defsystem.lisp"

;;; Loading #P"/Applications/sage-5.1/local/lib/ecl/cmp.fas"

An error occurred during initialization:

LOAD: Could not load file #P"/Applications/sage-5.1/local/lib/ecl-11.1.1/cmp.fas" (Error: "dlopen(/Applications/sage-5.1/local/lib/ecl-11.1.1/cmp.fas, 10): bad rebase type 0 in /Applications/sage-5.1/local/lib/ecl-11.1.1/cmp.fas").

[François Bissey]

OK so it looks like ecl may have problems. Do I read correctly that you are
building sage in the /Applications folder of OS X?

Francois

[kfiz]

yes, I'm trying to build sage in the "Applications" folder.

[Dima Pasechnik]

On Thursday, 2 August 2012 23:00:23 UTC+8, kfiz wrote:

yes, I'm trying to build sage in the "Applications" folder.

I'm not a big OSX expert, but I might expect that one needs to use sudo sometimes  to change things there properly.

I would rather build in a "normal" user directory, and then move the whole tree to /Applications

[Michael Welsh]

On 3/08/2012, at 4:08 PM, Dima Pasechnik <dim...@gmail.com> wrote:
>
> On Thursday, 2 August 2012 23:00:23 UTC+8, kfiz wrote:
>>
>> yes, I'm trying to build sage in the "Applications" folder.
>
>
> I'm not a big OSX expert, but I might expect that one needs to use sudo
> sometimes to change things there properly.

In my experience, this has never happened. Some installs install with sudo (well, they ask for my password), but I've never needed it. Normally its used when applications install libraries and such in /Library instead of ~/Library (so every user can access them), but this doesn't happen with Sage.

[kfiz]

I tried to  build in a "normal" directory and that didn't work either. Guess I have some weird configuration on my machine, that I just can't get a hold of. At least installation with pre build binaries worked.

[kfiz]

After an extremely long and interesting journey I finally succeded in building sage-5.2 from source on my machine.

It turned out that I had to upgrade my Xcode version from Xcode 3.2.6 to Xcode 4.2. 

I figured that as my original trials always crashed during the linking stage of building gcc that probably my ln, as, libtools etc. where outdated.

So I checked for a cctools update (apples equivalent of binutils), which I got with the Xcode 4.2 install.

As far as building sage was concerned I compiled everything with gcc-4.6.0 to which I had upgraded in the meantime from gcc-4.2. 

Thanks to everyone for the support!