Tuesday, 26 January 2016 15:53:27 UTC, Dima Pasechnik wrote: > > however, notice no path in front of > > libcliquer.dylib (compatibility version 0.0.0, current version 0.0.0) > argh, sorry, typo:
On a non-working copy I have libcliquer.so (compatibility version 0.0.0, current version 0.0.0) > in these outputs. > On a working copy of Sage I have > > > /Applications/SageMath/local/lib/libcliquer.dylib (compatibility version > 0.0.0, current version 0.0.0) > > > On Tuesday, 26 January 2016 15:46:17 UTC, Dima Pasechnik wrote: >> >> that is before the 1st Sage start attempt; and after it crashed, I get >> seemingly normal looking >> >> >> $ otool -L >> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so >> >> >> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so: >> >> libcliquer.so (compatibility version 0.0.0, current version 0.0.0) >> >> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version >> 1226.10.1) >> >> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version >> 1.0.0, current version 1.0.0) >> >> >> $ otool -L /Applications/SageMath/local/lib/libcliquer.so >> >> /Applications/SageMath/local/lib/libcliquer.so: >> >> libcliquer.so (compatibility version 0.0.0, current version 0.0.0) >> >> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version >> 1226.10.1) >> >> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version >> 1.0.0, current version 1.0.0) >> >> >> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib >> >> /Applications/SageMath/local/lib/libcliquer.dylib: >> >> libcliquer.so (compatibility version 0.0.0, current version 0.0.0) >> >> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version >> 1226.10.1) >> >> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version >> 1.0.0, current version 1.0.0) >> >> >> thus, my guess about the wrong arch seems to be right. >> >> On Tuesday, 26 January 2016 15:31:19 UTC, Dima Pasechnik wrote: >>> >>> >>> >>> On Tuesday, 26 January 2016 14:38:41 UTC, Volker Braun wrote: >>>> >>>> Output of "otool -L" for cliquer.so and libcliquer.so? >>>> >>> >>> here you are, there is some buildslave crap (how can it work on ANY >>> system?) >>> >>> $ otool -L >>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so >>> >>> >>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so: >>> >>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0) >>> >>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version >>> 1226.10.1) >>> >>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib >>> >>> (compatibility version 1.0.0, current version 1.0.0) >>> >>> >>> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib >>> >>> /Applications/SageMath/local/lib/libcliquer.dylib: >>> >>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0) >>> >>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version >>> 1226.10.1) >>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib >>> >>> (compatibility version 1.0.0, current version 1.0.0) >>> >>> $ otool -L /Applications/SageMath/local/lib/libcliquer.so >>> >>> /Applications/SageMath/local/lib/libcliquer.so: >>> >>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0) >>> >>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version >>> 1226.10.1) >>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib >>> >>> (compatibility version 1.0.0, current version 1.0.0) >>> >>> ------ >>> and libgcc_s.1.dylib should be >>> >>> >>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version >>> 1.0.0, current version 1.0.0) >>> >>> >>> >>>> >>>> >>>> On Tuesday, January 26, 2016 at 8:04:33 AM UTC-5, Dima Pasechnik wrote: >>>>> >>>>> I can reproduce this. I downloaded the >>>>> ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg >>>>> unpacked and copied in /Applications/ >>>>> and started /Applications/Sage/sage in the terminal. And ended up with >>>>> the same crash on clique.so load. >>>>> >>>>> It could be due to old hardware: >>>>> >>>>> MacBook Air (13-inch, Late 2010) >>>>> >>>>> Model Name: MacBook Air >>>>> >>>>> Model Identifier: MacBookAir3,2 >>>>> >>>>> Processor Name: Intel Core 2 Duo >>>>> >>>>> Processor Speed: 1.86 GHz >>>>> >>>>> Number of Processors: 1 >>>>> >>>>> Total Number of Cores: 2 >>>>> >>>>> L2 Cache: 6 MB >>>>> >>>>> Memory: 4 GB >>>>> >>>>> Bus Speed: 1.07 GHz >>>>> >>>>> Boot ROM Version: MBA31.0061.B01 >>>>> >>>>> SMC Version (system): 1.66f61 >>>>> >>>>> I don't know on which hardware the binary distro was built, I suspect >>>>> on something newer (Core2 Duo is really old and a bit weird). >>>>> It might be missing some processor commands which are used in the >>>>> binary... >>>>> >>>>> >>>>> Solution: rebuild Sage from source. >>>>> >>>>> Dima >>>>> >>>>> >>>>> On Tuesday, 26 January 2016 02:15:38 UTC, Volker Braun wrote: >>>>>> >>>>>> Does the file exist? From the log: >>>>>> >>>>>> ImportError: >>>>>> dlopen(/Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so, >>>>>> >>>>>> 2): Library not loaded: libcliquer.so >>>>>> Referenced from: >>>>>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so >>>>>> Reason: image not found >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Monday, January 25, 2016 at 7:52:42 PM UTC-5, Juan Luis Varona >>>>>> wrote: >>>>>>> >>>>>>> I have tried to install sage 7.0 in a mac with osx-10-11-2 and it >>>>>>> crashes. >>>>>>> >>>>>>> >>>>>>> ┌────────────────────────────────────────────────────────────────────┐ >>>>>>> >>>>>>> │ SageMath Version 7.0, Release Date: 2016-01-19 >>>>>>> │ >>>>>>> >>>>>>> │ Type "notebook()" for the browser-based notebook interface. >>>>>>> │ >>>>>>> >>>>>>> │ Type "help()" for help. >>>>>>> │ >>>>>>> >>>>>>> >>>>>>> └────────────────────────────────────────────────────────────────────┘ >>>>>>> >>>>>>> This looks like the first time you are running Sage. >>>>>>> >>>>>>> Updating various hardcoded paths... >>>>>>> >>>>>>> (Please wait at most a few minutes.) >>>>>>> >>>>>>> DO NOT INTERRUPT THIS. >>>>>>> >>>>>>> Done updating paths. >>>>>>> >>>>>>> >>>>>>> >>>>>>> ********************************************************************** >>>>>>> >>>>>>> >>>>>>> Oops, Sage crashed. We do our best to make it stable, but... >>>>>>> >>>>>>> [...] >>>>>>> >>>>>>> I have tried both with >>>>>>> *sage-7.0-OSX_10.11.2-x86_64.dmg >>>>>>> <ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg>* >>>>>>> and with >>>>>>> *sage-7.0-OSX_10.11.2-x86_64.app.dmg >>>>>>> <ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.app.dmg>* >>>>>>> >>>>>>> I include Sage_crash_report.txt >>>>>>> >>>>>>> Yours, >>>>>>> >>>>>>> Juan Luis Varona >>>>>>> >>>>>>> -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
