Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[kcrisman]

>
>
> I upgraded to Mac OS 10.11 this afternoon.  I tried running sage -b and 
> found the following error:
>
> -bash:/Applications/sage/src/sage $ sage -b
> python -u setup.py install
> Traceback (most recent call last):
>   File "setup.py", line 4, in 
> import os, sys, time, errno, platform, subprocess, glob
>   File "/Applications/sage/local/lib/python/subprocess.py", line 430, in 
> 
> import pickle
>   File "/Applications/sage/local/lib/python/pickle.py", line 34, in 
> 
> import struct
>   File "/Applications/sage/local/lib/python/struct.py", line 1, in 
> from _struct import *
> ImportError: 
> dlopen(/Applications/sage/local/lib/python2.7/lib-dynload/_struct.so, 2): 
> Symbol not found: _PyUnicodeUCS4_AsEncodedString
>   Referenced from: 
> /Applications/sage/local/lib/python2.7/lib-dynload/_struct.so
>   Expected in: flat namespace
>  in /Applications/sage/local/lib/python2.7/lib-dynload/_struct.so
> make: *** [sage] Error 1
>
> I followed the advice to reboot with command-R and ran the 'csrutil 
> disable' command in the terminal window.  Next time I tried it worked.
>
> Thanks!
>
>>

Is that a sustainable solution for everyone?  (I assume not, e.g. those who 
only use the notebook.)  Also, some people may not have access to that 
command if their computer is locked down by an employer (or would this 
escape the notice?).

Maybe at the very least there should be a big warning on the download page 
to not use El Capitan (yet). 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Volker Braun]

On Saturday, October 3, 2015 at 10:49:03 AM UTC+2, kcrisman wrote:

> Is that a sustainable solution for everyone?


No its not, we can't go around telling people to disable Apple's system 
integrity protection.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[William Stein]

Hi,

In the meantime, I think ASAP on the OS X binary download page we should:

 (1) move the "Usage:" message to the top (it's *hidden* at the bottom
where nobody will ever see it).

 (2) add that there is no way to run Sage on 10.11 except to either
disable Apple's system integrity protection, or use a virtual machine
running Linux.

When I searched around for info about "system integrity protection" I
hit numerous other software websites with similar warnings and
notices.

William

On Sat, Oct 3, 2015 at 9:47 AM, Dima Pasechnik  wrote:
>
>
> On Saturday, 3 October 2015 01:56:21 UTC-7, Volker Braun wrote:
>>
>> On Saturday, October 3, 2015 at 10:49:03 AM UTC+2, kcrisman wrote:
>>>
>>> Is that a sustainable solution for everyone?
>>
>>
>> No its not, we can't go around telling people to disable Apple's system
>> integrity protection.
>
>
> OK, so let's talk about switching to rpath then. Is it basically just
> tweaking of parameters passed to gcc (as a linker)? Do autotools know about
> them?
> Do we need extra tools (or convoluted calls to linker etc) on OSX?
> Can we keep the LD_*_PATH* functionality, to use it on Cygwin?
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



-- 
William (http://wstein.org)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Hal Snyder]

If switching to rpath starts up, it could be a great learning opportunity
for those of us who want to ramp up on the Sage build system. It would be
great if project wizards leave a trail for others to catch up & help with
testing.

I have done sage builds on Mac over the last couple years & several times
ran into time-consuming challenges.

On Sat, Oct 3, 2015 at 12:27 PM, William Stein  wrote:

> Hi,
>
> In the meantime, I think ASAP on the OS X binary download page we should:
>
>  (1) move the "Usage:" message to the top (it's *hidden* at the bottom
> where nobody will ever see it).
>
>  (2) add that there is no way to run Sage on 10.11 except to either
> disable Apple's system integrity protection, or use a virtual machine
> running Linux.
>
> When I searched around for info about "system integrity protection" I
> hit numerous other software websites with similar warnings and
> notices.
>
> William
>
> On Sat, Oct 3, 2015 at 9:47 AM, Dima Pasechnik  wrote:
> >
> >
> > On Saturday, 3 October 2015 01:56:21 UTC-7, Volker Braun wrote:
> >>
> >> On Saturday, October 3, 2015 at 10:49:03 AM UTC+2, kcrisman wrote:
> >>>
> >>> Is that a sustainable solution for everyone?
> >>
> >>
> >> No its not, we can't go around telling people to disable Apple's system
> >> integrity protection.
> >
> >
> > OK, so let's talk about switching to rpath then. Is it basically just
> > tweaking of parameters passed to gcc (as a linker)? Do autotools know
> about
> > them?
> > Do we need extra tools (or convoluted calls to linker etc) on OSX?
> > Can we keep the LD_*_PATH* functionality, to use it on Cygwin?
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to sage-devel+unsubscr...@googlegroups.com.
> > To post to this group, send email to sage-devel@googlegroups.com.
> > Visit this group at http://groups.google.com/group/sage-devel.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> William (http://wstein.org)
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/OBv5x1v3_6M/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Dima Pasechnik]

On Saturday, 3 October 2015 01:56:21 UTC-7, Volker Braun wrote:
>
> On Saturday, October 3, 2015 at 10:49:03 AM UTC+2, kcrisman wrote:
>
>> Is that a sustainable solution for everyone?
>
>
> No its not, we can't go around telling people to disable Apple's system 
> integrity protection.
>

OK, so let's talk about switching to rpath then. Is it basically just 
tweaking of parameters passed to gcc (as a linker)? Do autotools know about 
them?
Do we need extra tools (or convoluted calls to linker etc) on OSX? 
Can we keep the LD_*_PATH* functionality, to use it on Cygwin?


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[moep]

Thanks for the post!

Do you know if "disabling rootless" changes anything else for the daily use?


On Friday, October 2, 2015 at 11:00:23 AM UTC+2, Fredrik Strömberg wrote:
>
> After upgrading to El Capitan yesterday my sage ( v6.8 compiled from 
> source) stopped working and I figured out that  DYLD_LIBRARY_PATH and 
> LD_LIBRARY_PATH are no longer supported by default due to SIP (system 
> integrity protection) and rootless which are no turned on by default.
> After disabling rootless (boot into recovery mode with CMD+R and run 'csrutil 
> disable' from command line) everything works for me. 
> You can try and see if this also works for the downloaded binary 
> distributions.
> As a temporary measure this might be ok but in the long run something 
> probably have to change with the install process, e.g. rpaths as suggested 
> by others.
>
> Fredrik
>
> On Thursday, October 1, 2015 at 3:25:00 PM UTC+1, Thomas Kahle wrote:
>>
>> This is probably going to escalate with the public release of El Capitan. 
>> I upgraded, and I have no local sage anymore. What can we do?  I don't want 
>> to use sage math cloud, at least not always.
>>
>> On Friday, September 11, 2015 at 10:02:36 AM UTC+2, Volker Braun wrote:
>>>
>>> Looks like Apple kept the new behavior of DYLD_* environment variables 
>>> and they are not passed down to launched interpreters. Hence sooner or 
>>> later we crash with symbol not found as libraries can't be located. Really 
>>> we should have switched to rpaths years ago, this would have saved so much 
>>> pain. Also would explain why homebrew and friends didn't trip over that. 
>>> Don't know of any workaround on 10.11 besides sourcing sage-env whenever a 
>>> subshell is launched.
>>>
>>>
>>>
>>> On Friday, September 11, 2015 at 4:48:25 AM UTC+2, François wrote:

 Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to 
 that library. 
 I am guessing it is supposed to be dlopen-ed from python which would 
 supply 
 the symbol. I suspect python will need patching. 
 Can you start python from a sage shell? 

 François 

 > On 11/09/2015, at 14:40, Juan Luis Varona  
 wrote: 
 > 
 > 
 >> El 11 sept 2015, a las 4:24, kcrisman  escribió: 
 >> 
 >> But, usually, new versions of osx can execute already compiled 
 versions of sage, and this does not happen this time. (I like to have 
 always the last version of osx in one of my computers, and I do not 
 remember this problem in the past.) 
 >> 
 >> 
 >> Yes, good point.  Can you give us exactly what kind of problems you 
 encounter with the 10.10 version on 10.11?  (If there are any message at 
 all.) 
 >> 
 > 
 > This is what appears in the Terminal using Sage-6.8.app (compiled for 
 osx 10.10) under osx 10.11: 
 > 
 > - 
 > 
 > Last login: Thu Sep 10 18:37:14 on ttys000 
 > AirTeXano:~ jvarona$ 
 '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
 > Traceback (most recent call last): 
 >  File 
 "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook",
  
 line 7, in  
 >import argparse 
 >  File 
 "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
  
 line 85, in  
 >import collections as _collections 
 >  File 
 "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
  
 line 9, in  
 >from operator import itemgetter as _itemgetter, eq as _eq 
 > ImportError: 
 dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
  
 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
 >  Referenced from: 
 /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
  

 >  Expected in: flat namespace 
 > in 
 /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
  

 > AirTeXano:~ jvarona$ 
 > 
 >  
 > 
 > Juan Luis 
 > 
 > 
 > -- 
 > You received this message because you are subscribed to the Google 
 Groups "sage-devel" group. 
 > To unsubscribe from this group and stop receiving emails from it, 
 send an email to sage-devel+...@googlegroups.com. 
 > To post to this group, send email to sage-...@googlegroups.com. 
 > Visit this group at http://groups.google.com/group/sage-devel. 
 > For more options, visit https://groups.google.com/d/optout. 




-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to 

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[David Roe]

My impression is that it's a new security feature for 10.11, preventing any
programs (even ones that have root privileges) from writing to certain
system folders.  So as long as you don't run into any such malware,
disabling rootless should have no effect on you.  :-)
David

On Fri, Oct 2, 2015 at 7:10 PM, moep  wrote:

> Thanks for the post!
>
> Do you know if "disabling rootless" changes anything else for the daily
> use?
>
>
>
> On Friday, October 2, 2015 at 11:00:23 AM UTC+2, Fredrik Strömberg wrote:
>>
>> After upgrading to El Capitan yesterday my sage ( v6.8 compiled from
>> source) stopped working and I figured out that  DYLD_LIBRARY_PATH and
>> LD_LIBRARY_PATH are no longer supported by default due to SIP (system
>> integrity protection) and rootless which are no turned on by default.
>> After disabling rootless (boot into recovery mode with CMD+R and run 'csrutil
>> disable' from command line) everything works for me.
>> You can try and see if this also works for the downloaded binary
>> distributions.
>> As a temporary measure this might be ok but in the long run something
>> probably have to change with the install process, e.g. rpaths as suggested
>> by others.
>>
>> Fredrik
>>
>> On Thursday, October 1, 2015 at 3:25:00 PM UTC+1, Thomas Kahle wrote:
>>>
>>> This is probably going to escalate with the public release of El
>>> Capitan. I upgraded, and I have no local sage anymore. What can we do?  I
>>> don't want to use sage math cloud, at least not always.
>>>
>>> On Friday, September 11, 2015 at 10:02:36 AM UTC+2, Volker Braun wrote:

 Looks like Apple kept the new behavior of DYLD_* environment variables
 and they are not passed down to launched interpreters. Hence sooner or
 later we crash with symbol not found as libraries can't be located. Really
 we should have switched to rpaths years ago, this would have saved so much
 pain. Also would explain why homebrew and friends didn't trip over that.
 Don't know of any workaround on 10.11 besides sourcing sage-env whenever a
 subshell is launched.



 On Friday, September 11, 2015 at 4:48:25 AM UTC+2, François wrote:
>
> Hum, that symbol is in libpython2.7.dylib, operator.so is not linked
> to that library.
> I am guessing it is supposed to be dlopen-ed from python which would
> supply
> the symbol. I suspect python will need patching.
> Can you start python from a sage shell?
>
> François
>
> > On 11/09/2015, at 14:40, Juan Luis Varona 
> wrote:
> >
> >
> >> El 11 sept 2015, a las 4:24, kcrisman 
> escribió:
> >>
> >> But, usually, new versions of osx can execute already compiled
> versions of sage, and this does not happen this time. (I like to have
> always the last version of osx in one of my computers, and I do not
> remember this problem in the past.)
> >>
> >>
> >> Yes, good point.  Can you give us exactly what kind of problems you
> encounter with the 10.10 version on 10.11?  (If there are any message at
> all.)
> >>
> >
> > This is what appears in the Terminal using Sage-6.8.app (compiled
> for osx 10.10) under osx 10.11:
> >
> > -
> >
> > Last login: Thu Sep 10 18:37:14 on ttys000
> > AirTeXano:~ jvarona$
> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook
> > Traceback (most recent call last):
> >  File
> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook",
> line 7, in 
> >import argparse
> >  File
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
> line 85, in 
> >import collections as _collections
> >  File
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
> line 9, in 
> >from operator import itemgetter as _itemgetter, eq as _eq
> > ImportError:
> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
> 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString
> >  Referenced from:
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>
> >  Expected in: flat namespace
> > in
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>
> > AirTeXano:~ jvarona$
> >
> > 
> >
> > Juan Luis
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send an email to sage-devel+...@googlegroups.com.
> > To post to this group, send email to sage-...@googlegroups.com.
> > Visit this group at http://groups.google.com/group/sage-devel.
> > For 

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Fredrik Strömberg]

After upgrading to El Capitan yesterday my sage ( v6.8 compiled from 
source) stopped working and I figured out that  DYLD_LIBRARY_PATH and 
LD_LIBRARY_PATH are no longer supported by default due to SIP (system 
integrity protection) and rootless which are no turned on by default.
After disabling rootless (boot into recovery mode with CMD+R and run 'csrutil 
disable' from command line) everything works for me. 
You can try and see if this also works for the downloaded binary 
distributions.
As a temporary measure this might be ok but in the long run something 
probably have to change with the install process, e.g. rpaths as suggested 
by others.

Fredrik

On Thursday, October 1, 2015 at 3:25:00 PM UTC+1, Thomas Kahle wrote:
>
> This is probably going to escalate with the public release of El Capitan. 
> I upgraded, and I have no local sage anymore. What can we do?  I don't want 
> to use sage math cloud, at least not always.
>
> On Friday, September 11, 2015 at 10:02:36 AM UTC+2, Volker Braun wrote:
>>
>> Looks like Apple kept the new behavior of DYLD_* environment variables 
>> and they are not passed down to launched interpreters. Hence sooner or 
>> later we crash with symbol not found as libraries can't be located. Really 
>> we should have switched to rpaths years ago, this would have saved so much 
>> pain. Also would explain why homebrew and friends didn't trip over that. 
>> Don't know of any workaround on 10.11 besides sourcing sage-env whenever a 
>> subshell is launched.
>>
>>
>>
>> On Friday, September 11, 2015 at 4:48:25 AM UTC+2, François wrote:
>>>
>>> Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to 
>>> that library. 
>>> I am guessing it is supposed to be dlopen-ed from python which would 
>>> supply 
>>> the symbol. I suspect python will need patching. 
>>> Can you start python from a sage shell? 
>>>
>>> François 
>>>
>>> > On 11/09/2015, at 14:40, Juan Luis Varona  
>>> wrote: 
>>> > 
>>> > 
>>> >> El 11 sept 2015, a las 4:24, kcrisman  escribió: 
>>> >> 
>>> >> But, usually, new versions of osx can execute already compiled 
>>> versions of sage, and this does not happen this time. (I like to have 
>>> always the last version of osx in one of my computers, and I do not 
>>> remember this problem in the past.) 
>>> >> 
>>> >> 
>>> >> Yes, good point.  Can you give us exactly what kind of problems you 
>>> encounter with the 10.10 version on 10.11?  (If there are any message at 
>>> all.) 
>>> >> 
>>> > 
>>> > This is what appears in the Terminal using Sage-6.8.app (compiled for 
>>> osx 10.10) under osx 10.11: 
>>> > 
>>> > - 
>>> > 
>>> > Last login: Thu Sep 10 18:37:14 on ttys000 
>>> > AirTeXano:~ jvarona$ 
>>> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
>>> > Traceback (most recent call last): 
>>> >  File 
>>> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
>>> line 7, in  
>>> >import argparse 
>>> >  File 
>>> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
>>>  
>>> line 85, in  
>>> >import collections as _collections 
>>> >  File 
>>> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
>>>  
>>> line 9, in  
>>> >from operator import itemgetter as _itemgetter, eq as _eq 
>>> > ImportError: 
>>> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
>>>  
>>> 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
>>> >  Referenced from: 
>>> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>>>  
>>>
>>> >  Expected in: flat namespace 
>>> > in 
>>> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>>>  
>>>
>>> > AirTeXano:~ jvarona$ 
>>> > 
>>> >  
>>> > 
>>> > Juan Luis 
>>> > 
>>> > 
>>> > -- 
>>> > You received this message because you are subscribed to the Google 
>>> Groups "sage-devel" group. 
>>> > To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sage-devel+...@googlegroups.com. 
>>> > To post to this group, send email to sage-...@googlegroups.com. 
>>> > Visit this group at http://groups.google.com/group/sage-devel. 
>>> > For more options, visit https://groups.google.com/d/optout. 
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Dima Pasechnik]

On Thursday, 1 October 2015 11:51:04 UTC-7, Dima Pasechnik wrote:
>
> On Thursday, 1 October 2015 07:39:51 UTC-7, Hal Snyder wrote:
>>
>> On Friday, September 11, 2015 at 3:02:36 AM UTC-5, Volker Braun wrote:
>>>
>>> Looks like Apple kept the new behavior of DYLD_* environment variables 
>>> and they are not passed down to launched interpreters. Hence sooner or 
>>> later we crash with symbol not found as libraries can't be located. Really 
>>> we should have switched to rpaths years ago, this would have saved so much 
>>> pain. Also would explain why homebrew and friends didn't trip over that. 
>>> Don't know of any workaround on 10.11 besides sourcing sage-env whenever a 
>>> subshell is launched.
>>>
>>> What's involved in switching to rpaths? What would be the main 
>> advantages?
>>
>
> in a nutshell, rpaths are relative paths, telling the linker to search for 
> extra dependencies,
> written into library/executives binaries, and allow you
> to avoid  depending on the execution environment; apparently it's very 
> easy to create on 
> Linux, but not so on OSX, where you need to jump some hoops.
> People wrote tools to fix the latter, such as
> https://github.com/auriamg/macdylibbundler/
>
> Thus, it would mean no more runtime linking to a wrong library due to 
> wrong (DY)LD_LIBRARY_PATH
> and the latter doesn't work (at all?) on OSX11, as far as I understand.
>
> this would also mean that the Cygwin port will have to stay with 
LD_LIBRARY_PATH, as rpath
is not supported on Cygwin.


 

> Dima
>  
>
>>  
>>
>>>
>>> ...
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Mike Zabrocki]

Hi, Let me pile on and explain my experience and how you have already fixed 
my problem.

I upgraded to Mac OS 10.11 this afternoon.  I tried running sage -b and 
found the following error:

-bash:/Applications/sage/src/sage $ sage -b
python -u setup.py install
Traceback (most recent call last):
  File "setup.py", line 4, in 
import os, sys, time, errno, platform, subprocess, glob
  File "/Applications/sage/local/lib/python/subprocess.py", line 430, in 

import pickle
  File "/Applications/sage/local/lib/python/pickle.py", line 34, in 
import struct
  File "/Applications/sage/local/lib/python/struct.py", line 1, in 
from _struct import *
ImportError: 
dlopen(/Applications/sage/local/lib/python2.7/lib-dynload/_struct.so, 2): 
Symbol not found: _PyUnicodeUCS4_AsEncodedString
  Referenced from: 
/Applications/sage/local/lib/python2.7/lib-dynload/_struct.so
  Expected in: flat namespace
 in /Applications/sage/local/lib/python2.7/lib-dynload/_struct.so
make: *** [sage] Error 1

I followed the advice to reboot with command-R and ran the 'csrutil 
disable' command in the terminal window.  Next time I tried it worked.

Thanks!

On Friday, 2 October 2015 04:00:23 UTC-5, Fredrik Strömberg wrote:
>
> After upgrading to El Capitan yesterday my sage ( v6.8 compiled from 
> source) stopped working and I figured out that  DYLD_LIBRARY_PATH and 
> LD_LIBRARY_PATH are no longer supported by default due to SIP (system 
> integrity protection) and rootless which are no turned on by default.
> After disabling rootless (boot into recovery mode with CMD+R and run 'csrutil 
> disable' from command line) everything works for me. 
> You can try and see if this also works for the downloaded binary 
> distributions.
> As a temporary measure this might be ok but in the long run something 
> probably have to change with the install process, e.g. rpaths as suggested 
> by others.
>
> Fredrik
>
> On Thursday, October 1, 2015 at 3:25:00 PM UTC+1, Thomas Kahle wrote:
>>
>> This is probably going to escalate with the public release of El Capitan. 
>> I upgraded, and I have no local sage anymore. What can we do?  I don't want 
>> to use sage math cloud, at least not always.
>>
>> On Friday, September 11, 2015 at 10:02:36 AM UTC+2, Volker Braun wrote:
>>>
>>> Looks like Apple kept the new behavior of DYLD_* environment variables 
>>> and they are not passed down to launched interpreters. Hence sooner or 
>>> later we crash with symbol not found as libraries can't be located. Really 
>>> we should have switched to rpaths years ago, this would have saved so much 
>>> pain. Also would explain why homebrew and friends didn't trip over that. 
>>> Don't know of any workaround on 10.11 besides sourcing sage-env whenever a 
>>> subshell is launched.
>>>
>>>
>>>
>>> On Friday, September 11, 2015 at 4:48:25 AM UTC+2, François wrote:

 Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to 
 that library. 
 I am guessing it is supposed to be dlopen-ed from python which would 
 supply 
 the symbol. I suspect python will need patching. 
 Can you start python from a sage shell? 

 François 

 > On 11/09/2015, at 14:40, Juan Luis Varona  
 wrote: 
 > 
 > 
 >> El 11 sept 2015, a las 4:24, kcrisman  escribió: 
 >> 
 >> But, usually, new versions of osx can execute already compiled 
 versions of sage, and this does not happen this time. (I like to have 
 always the last version of osx in one of my computers, and I do not 
 remember this problem in the past.) 
 >> 
 >> 
 >> Yes, good point.  Can you give us exactly what kind of problems you 
 encounter with the 10.10 version on 10.11?  (If there are any message at 
 all.) 
 >> 
 > 
 > This is what appears in the Terminal using Sage-6.8.app (compiled for 
 osx 10.10) under osx 10.11: 
 > 
 > - 
 > 
 > Last login: Thu Sep 10 18:37:14 on ttys000 
 > AirTeXano:~ jvarona$ 
 '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
 > Traceback (most recent call last): 
 >  File 
 "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook",
  
 line 7, in  
 >import argparse 
 >  File 
 "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
  
 line 85, in  
 >import collections as _collections 
 >  File 
 "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
  
 line 9, in  
 >from operator import itemgetter as _itemgetter, eq as _eq 
 > ImportError: 
 dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
  
 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
 >  Referenced from: 
 

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Thomas Kahle]

This is probably going to escalate with the public release of El Capitan. I 
upgraded, and I have no local sage anymore. What can we do?  I don't want 
to use sage math cloud, at least not always.

On Friday, September 11, 2015 at 10:02:36 AM UTC+2, Volker Braun wrote:
>
> Looks like Apple kept the new behavior of DYLD_* environment variables and 
> they are not passed down to launched interpreters. Hence sooner or later we 
> crash with symbol not found as libraries can't be located. Really we should 
> have switched to rpaths years ago, this would have saved so much pain. Also 
> would explain why homebrew and friends didn't trip over that. Don't know of 
> any workaround on 10.11 besides sourcing sage-env whenever a subshell is 
> launched.
>
>
>
> On Friday, September 11, 2015 at 4:48:25 AM UTC+2, François wrote:
>>
>> Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to 
>> that library. 
>> I am guessing it is supposed to be dlopen-ed from python which would 
>> supply 
>> the symbol. I suspect python will need patching. 
>> Can you start python from a sage shell? 
>>
>> François 
>>
>> > On 11/09/2015, at 14:40, Juan Luis Varona  
>> wrote: 
>> > 
>> > 
>> >> El 11 sept 2015, a las 4:24, kcrisman  escribió: 
>> >> 
>> >> But, usually, new versions of osx can execute already compiled 
>> versions of sage, and this does not happen this time. (I like to have 
>> always the last version of osx in one of my computers, and I do not 
>> remember this problem in the past.) 
>> >> 
>> >> 
>> >> Yes, good point.  Can you give us exactly what kind of problems you 
>> encounter with the 10.10 version on 10.11?  (If there are any message at 
>> all.) 
>> >> 
>> > 
>> > This is what appears in the Terminal using Sage-6.8.app (compiled for 
>> osx 10.10) under osx 10.11: 
>> > 
>> > - 
>> > 
>> > Last login: Thu Sep 10 18:37:14 on ttys000 
>> > AirTeXano:~ jvarona$ 
>> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
>> > Traceback (most recent call last): 
>> >  File 
>> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
>> line 7, in  
>> >import argparse 
>> >  File 
>> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
>>  
>> line 85, in  
>> >import collections as _collections 
>> >  File 
>> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
>>  
>> line 9, in  
>> >from operator import itemgetter as _itemgetter, eq as _eq 
>> > ImportError: 
>> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
>>  
>> 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
>> >  Referenced from: 
>> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>>  
>>
>> >  Expected in: flat namespace 
>> > in 
>> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>>  
>>
>> > AirTeXano:~ jvarona$ 
>> > 
>> >  
>> > 
>> > Juan Luis 
>> > 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> Groups "sage-devel" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an email to sage-devel+...@googlegroups.com. 
>> > To post to this group, send email to sage-...@googlegroups.com. 
>> > Visit this group at http://groups.google.com/group/sage-devel. 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Hal Snyder]

On Friday, September 11, 2015 at 3:02:36 AM UTC-5, Volker Braun wrote:
>
> Looks like Apple kept the new behavior of DYLD_* environment variables and 
> they are not passed down to launched interpreters. Hence sooner or later we 
> crash with symbol not found as libraries can't be located. Really we should 
> have switched to rpaths years ago, this would have saved so much pain. Also 
> would explain why homebrew and friends didn't trip over that. Don't know of 
> any workaround on 10.11 besides sourcing sage-env whenever a subshell is 
> launched.
>
>
> What's involved in switching to rpaths? What would be the main advantages?
 

>
> ...
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Dima Pasechnik]

On Thursday, 1 October 2015 07:39:51 UTC-7, Hal Snyder wrote:
>
> On Friday, September 11, 2015 at 3:02:36 AM UTC-5, Volker Braun wrote:
>>
>> Looks like Apple kept the new behavior of DYLD_* environment variables 
>> and they are not passed down to launched interpreters. Hence sooner or 
>> later we crash with symbol not found as libraries can't be located. Really 
>> we should have switched to rpaths years ago, this would have saved so much 
>> pain. Also would explain why homebrew and friends didn't trip over that. 
>> Don't know of any workaround on 10.11 besides sourcing sage-env whenever a 
>> subshell is launched.
>>
>> What's involved in switching to rpaths? What would be the main advantages?
>

in a nutshell, rpaths are relative paths, telling the linker to search for 
extra dependencies,
written into library/executives binaries, and allow you
to avoid  depending on the execution environment; apparently it's very easy 
to create on 
Linux, but not so on OSX, where you need to jump some hoops.
People wrote tools to fix the latter, such as
https://github.com/auriamg/macdylibbundler/

Thus, it would mean no more runtime linking to a wrong library due to wrong 
(DY)LD_LIBRARY_PATH
and the latter doesn't work (at all?) on OSX11, as far as I understand.

Dima
 

>  
>
>>
>> ...
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

Unfortunately, the compiling process of sage 6.9rc0 with xcode 7 under macosx 
10.11 has finished with errors:

—


Unhandled SIGSEGV: A segmentation fault occurred in Sage.
This probably occurred because a *compiled* component of Sage has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Sage will now terminate.

/Applications/sage-6.9.rc0/build/bin/sage-logger: line 32: 97809 Segmentation 
fault: 11  ./sage --docbuild --no-pdf-links all html
make[2]: *** [doc-html] Error 139
make[1]: *** [all] Error 2

real673m6.573s
user583m48.760s
sys 71m8.235s
***
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all'):

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

make: *** [all] Error 1

—

This is the complete log file (23 megas file):
https://dl.dropboxusercontent.com/u/8293746/log-compiling-sage69rc0-xcode7-macosx10.11.txt

And this is what I obtain executing sage:


┌┐
│ SageMath Version 6.9.rc0, Release Date: 2015-09-25 │
│ Type "notebook()" for the browser-based notebook interface.│
│ Type "help()" for help.│
└┘
┏┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗┛
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...

A crash report was automatically generated with the following information:
  - A verbatim copy of the crash traceback.
  - A copy of your input history during this session.
  - Data on your current Sage configuration.

It was left in the file named:
'/Users/jvarona/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt'
If you can email this file to the developers, the information in it will help
them in understanding and correcting the problem.

You can mail it to: sage-support at sage-supp...@googlegroups.com
with the subject 'Sage Crash Report'.

If you want to do it now, the following command will work (under Unix):
mail -s 'Sage Crash Report' sage-supp...@googlegroups.com < 
/Users/jvarona/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt

To ensure accurate tracking of this issue, please file a report about it at:
http://trac.sagemath.org


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

> 
> Post the Sage_crash_report.txt
> (Sage 6.9rc0 with xcode 7 under macosx 10.11)
> 

Here it is:

***

IPython post-mortem report

{'commit_hash': u'2f7c727',
 'commit_source': 'installation',
 'default_encoding': 'UTF-8',
 'ipython_path': 
'/Applications/sage-6.9.rc0/local/lib/python2.7/site-packages/IPython',
 'ipython_version': '4.0.0',
 'os_name': 'posix',
 'platform': 'Darwin-15.0.0-x86_64-i386-64bit',
 'sys_executable': '/Applications/sage-6.9.rc0/local/bin/python',
 'sys_platform': 'darwin',
 'sys_version': '2.7.9 (default, Sep 26 2015, 01:38:56) \n[GCC 4.9.2]'}

***



***

Crash traceback:

---
---
ImportError   Python 2.7.9: /Applications/sage-6.9.rc0/local/bin/python
   Sat Sep 26 13:33:08 2015
A problem occurred executing Python code.  Here is the sequence of function
calls leading up to the error, with the most recent (innermost) call last.
/Applications/sage-6.9.rc0/src/bin/sage-ipython in ()
  1 #!/usr/bin/env python
  2 # -*- coding: utf-8 -*-
  3 """
  4 Sage IPython startup script.
  5 """
  6 
  7 # Install extra readline commands before IPython initialization
  8 from sage.repl.readline_extra_commands import *
  9 
 10 from sage.repl.interpreter import SageTerminalApp
 11 
 12 app = SageTerminalApp.instance()
---> 13 app.initialize()
global app.initialize = >
 14 app.start()

/Applications/sage-6.9.rc0/local/lib/python2.7/site-packages/IPython/terminal/ipapp.pyc
 in initialize(self=, argv=None)

/Applications/sage-6.9.rc0/local/lib/python2.7/site-packages/traitlets/config/application.pyc
 in catch_config_error(method=, 
app=, *args=(None,), **kwargs={})
 60 
 61 
#-
 62 # Application class
 63 
#-
 64 
 65 @decorator
 66 def catch_config_error(method, app, *args, **kwargs):
 67 """Method decorator for catching invalid config 
(Trait/ArgumentErrors) during init.
 68 
 69 On a TraitError (generally caused by bad config), this will print 
the trait's
 70 message, and exit the app.
 71 
 72 For use on init methods, to prevent invoking excepthook on invalid 
input.
 73 """
 74 try:
---> 75 return method(app, *args, **kwargs)
method = 
app = 
args = (None,)
kwargs = {}
 76 except (TraitError, ArgumentError) as e:
 77 app.print_help()
 78 app.log.fatal("Bad config encountered during initialization:")
 79 app.log.fatal(str(e))
 80 app.log.debug("Config at the time: %s", app.config)
 81 app.exit(1)
 82 
 83 
 84 class ApplicationError(Exception):
 85 pass
 86 
 87 class LevelFormatter(logging.Formatter):
 88 """Formatter with additional `highlevel` record
 89 
 90 This field is empty if log level is less than highlevel_limit,

/Applications/sage-6.9.rc0/local/lib/python2.7/site-packages/IPython/terminal/ipapp.pyc
 in initialize(self=, argv=None)
299 
300 return super(TerminalIPythonApp, self).parse_command_line(argv)
301 
302 @catch_config_error
303 def initialize(self, argv=None):
304 """Do actions after construct, but before starting the app."""
305 super(TerminalIPythonApp, self).initialize(argv)
306 if self.subapp is not None:
307 # don't bother initializing further, starting subapp
308 return
309 # print self.extra_args
310 if self.extra_args and not self.something_to_run:
311 self.file_to_run = self.extra_args[0]
312 self.init_path()
313 # create the shell
--> 314 self.init_shell()
self.init_shell = >
315 # and draw the banner
316 self.init_banner()
317 # Now a variety of things that happen after the banner is 
printed.
318 self.init_gui_pylab()
319 self.init_extensions()
320 self.init_code()
321 
322 def init_shell(self):
323 """initialize the InteractiveShell instance"""
324 # Create an InteractiveShell instance.
325 # shell.display_banner should always be False for the terminal
326 # based app, because we call shell.show_banner() by hand below
327 # so the banner shows *before* all extension loading 

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Volker Braun]

Post the Sage_crash_report.txt

On Saturday, September 26, 2015 at 11:50:15 AM UTC+2, Juan Luis Varona 
wrote:
>
> Unfortunately, the compiling process of sage 6.9rc0 with xcode 7 under 
> macosx 10.11 has finished with errors: 
>
> — 
>
>  
> Unhandled SIGSEGV: A segmentation fault occurred in Sage. 
> This probably occurred because a *compiled* component of Sage has a bug 
> in it and is not properly wrapped with sig_on(), sig_off(). 
> Sage will now terminate. 
>  
> /Applications/sage-6.9.rc0/build/bin/sage-logger: line 32: 97809 
> Segmentation fault: 11  ./sage --docbuild --no-pdf-links all html 
> make[2]: *** [doc-html] Error 139 
> make[1]: *** [all] Error 2 
>
> real673m6.573s 
> user583m48.760s 
> sys71m8.235s 
> *** 
> Error building Sage. 
>
> The following package(s) may have failed to build (not necessarily 
> during this run of 'make all'): 
>
> The build directory may contain configuration files and other potentially 
> helpful information. WARNING: if you now run 'make' again, the build 
> directory will, by default, be deleted. Set the environment variable 
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. 
>
> make: *** [all] Error 1 
>
> — 
>
> This is the complete log file (23 megas file): 
>
> https://dl.dropboxusercontent.com/u/8293746/log-compiling-sage69rc0-xcode7-macosx10.11.txt
>  
>
> And this is what I obtain executing sage: 
>
>
> ┌┐ 
> │ SageMath Version 6.9.rc0, Release Date: 2015-09-25 │ 
> │ Type "notebook()" for the browser-based notebook interface.│ 
> │ Type "help()" for help.│ 
> └┘ 
> ┏┓ 
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃ 
> ┗┛ 
> 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... 
>
> A crash report was automatically generated with the following information: 
>   - A verbatim copy of the crash traceback. 
>   - A copy of your input history during this session. 
>   - Data on your current Sage configuration. 
>
> It was left in the file named: 
> '/Users/jvarona/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt' 
>
> If you can email this file to the developers, the information in it will 
> help 
> them in understanding and correcting the problem. 
>
> You can mail it to: sage-support at sage-s...@googlegroups.com 
>  
> with the subject 'Sage Crash Report'. 
>
> If you want to do it now, the following command will work (under Unix): 
> mail -s 'Sage Crash Report' sage-s...@googlegroups.com  < 
> /Users/jvarona/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt 
>
> To ensure accurate tracking of this issue, please file a report about it 
> at: 
> http://trac.sagemath.org 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[John H Palmieri]

Please try the latest Sage prerelease (6.9.rc0, available here: 
http://files.sagemath.org/devel/index.html) should build with Xcode 7, so I 
hope it builds with OS X 10.11.

  John


On Friday, September 18, 2015 at 8:14:44 AM UTC-7, John H Palmieri wrote:
>
>
>
> On Friday, September 18, 2015 at 2:01:24 AM UTC-7, Juan Luis Varona wrote:
>>
>> Actually, xcode 7 were released yesterday. 
>>
>> I can confirm that again sage 6.8 cannot be compiled in mac os x 10.11 
>> with xcode 7. 
>>
>> Juan Luis 
>>
>
> We are tracking build issues with Xcode 7 here: 
> http://trac.sagemath.org/ticket/19232. I hope fixing those will fix the 
> problems on OS X 10.11.
>
>   John
>
>
>> > 
>> > Same problem, nobody find a solution ? If yes, please can you tell me 
>> how ! 
>> > 
>> > Charles 
>> > 
>> > Le vendredi 11 septembre 2015 04:48:25 UTC+2, François a écrit : 
>> > Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to 
>> that library. 
>> > I am guessing it is supposed to be dlopen-ed from python which would 
>> supply 
>> > the symbol. I suspect python will need patching. 
>> > Can you start python from a sage shell? 
>> > 
>> > François 
>> > 
>> > > On 11/09/2015, at 14:40, Juan Luis Varona  
>> wrote: 
>> > > 
>> > > 
>> > >> El 11 sept 2015, a las 4:24, kcrisman  escribió: 
>> > >> 
>> > >> But, usually, new versions of osx can execute already compiled 
>> versions of sage, and this does not happen this time. (I like to have 
>> always the last version of osx in one of my computers, and I do not 
>> remember this problem in the past.) 
>> > >> 
>> > >> 
>> > >> Yes, good point.  Can you give us exactly what kind of problems you 
>> encounter with the 10.10 version on 10.11?  (If there are any message at 
>> all.) 
>> > >> 
>> > > 
>> > > This is what appears in the Terminal using Sage-6.8.app (compiled for 
>> osx 10.10) under osx 10.11: 
>> > > 
>> > > - 
>> > > 
>> > > Last login: Thu Sep 10 18:37:14 on ttys000 
>> > > AirTeXano:~ jvarona$ 
>> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
>> > > Traceback (most recent call last): 
>> > >  File 
>> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
>> line 7, in  
>> > >import argparse 
>> > >  File 
>> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
>>  
>> line 85, in  
>> > >import collections as _collections 
>> > >  File 
>> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
>>  
>> line 9, in  
>> > >from operator import itemgetter as _itemgetter, eq as _eq 
>> > > ImportError: 
>> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
>>  
>> 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
>> > >  Referenced from: 
>> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>>  
>>
>> > >  Expected in: flat namespace 
>> > > in 
>> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>>  
>>
>> > > AirTeXano:~ jvarona$ 
>> > > 
>> > >  
>> > > 
>> > > Juan Luis 
>> > > 
>> > > 
>> > > -- 
>> > > You received this message because you are subscribed to the Google 
>> Groups "sage-devel" group. 
>> > > To unsubscribe from this group and stop receiving emails from it, 
>> send an email to sage-devel+...@googlegroups.com. 
>> > > To post to this group, send email to sage-...@googlegroups.com. 
>> > > Visit this group at http://groups.google.com/group/sage-devel. 
>> > > For more options, visit https://groups.google.com/d/optout. 
>> > 
>> > 
>> > -- 
>> > You received this message because you are subscribed to a topic in the 
>> Google Groups "sage-devel" group. 
>> > To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/sage-devel/OBv5x1v3_6M/unsubscribe. 
>> > To unsubscribe from this group and all its topics, send an email to 
>> sage-devel+...@googlegroups.com. 
>> > To post to this group, send email to sage-...@googlegroups.com. 
>> > Visit this group at http://groups.google.com/group/sage-devel. 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

I have downlodaded 6.9.rc0 and I my computer is now compiling with xcode 7 on 
osx 11.10.

I will inform at the end of the process,

Juan Luis

> El 25 sept 2015, a las 17:12, John H Palmieri  
> escribió:
> 
> Please try the latest Sage prerelease (6.9.rc0, available here: 
> http://files.sagemath.org/devel/index.html) should build with Xcode 7, so I 
> hope it builds with OS X 10.11.
> 
>   John
> 
> 
> On Friday, September 18, 2015 at 8:14:44 AM UTC-7, John H Palmieri wrote:
> 
> 
> On Friday, September 18, 2015 at 2:01:24 AM UTC-7, Juan Luis Varona wrote:
> Actually, xcode 7 were released yesterday. 
> 
> I can confirm that again sage 6.8 cannot be compiled in mac os x 10.11 with 
> xcode 7. 
> 
> Juan Luis 
> 
> We are tracking build issues with Xcode 7 here: 
> http://trac.sagemath.org/ticket/19232. I hope fixing those will fix the 
> problems on OS X 10.11.
> 
>   John
> 
> 
> > 
> > Same problem, nobody find a solution ? If yes, please can you tell me how ! 
> > 
> > Charles 
> > 
> > Le vendredi 11 septembre 2015 04:48:25 UTC+2, François a écrit : 
> > Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to 
> > that library. 
> > I am guessing it is supposed to be dlopen-ed from python which would supply 
> > the symbol. I suspect python will need patching. 
> > Can you start python from a sage shell? 
> > 
> > François 
> > 
> > > On 11/09/2015, at 14:40, Juan Luis Varona  wrote: 
> > > 
> > > 
> > >> El 11 sept 2015, a las 4:24, kcrisman  escribió: 
> > >> 
> > >> But, usually, new versions of osx can execute already compiled versions 
> > >> of sage, and this does not happen this time. (I like to have always the 
> > >> last version of osx in one of my computers, and I do not remember this 
> > >> problem in the past.) 
> > >> 
> > >> 
> > >> Yes, good point.  Can you give us exactly what kind of problems you 
> > >> encounter with the 10.10 version on 10.11?  (If there are any message at 
> > >> all.) 
> > >> 
> > > 
> > > This is what appears in the Terminal using Sage-6.8.app (compiled for osx 
> > > 10.10) under osx 10.11: 
> > > 
> > > - 
> > > 
> > > Last login: Thu Sep 10 18:37:14 on ttys000 
> > > AirTeXano:~ jvarona$ 
> > > '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
> > > Traceback (most recent call last): 
> > >  File 
> > > "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook",
> > >  line 7, in  
> > >import argparse 
> > >  File 
> > > "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
> > >  line 85, in  
> > >import collections as _collections 
> > >  File 
> > > "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
> > >  line 9, in  
> > >from operator import itemgetter as _itemgetter, eq as _eq 
> > > ImportError: 
> > > dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
> > >  2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
> > >  Referenced from: 
> > > /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
> > >  
> > >  Expected in: flat namespace 
> > > in 
> > > /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
> > >  
> > > AirTeXano:~ jvarona$ 
> > > 
> > >  
> > > 
> > > Juan Luis 
> > > 
> > > 
> > > -- 
> > > You received this message because you are subscribed to the Google Groups 
> > > "sage-devel" group. 
> > > To unsubscribe from this group and stop receiving emails from it, send an 
> > > email to sage-devel+...@googlegroups.com. 
> > > To post to this group, send email to sage-...@googlegroups.com. 
> > > Visit this group at http://groups.google.com/group/sage-devel. 
> > > For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to a topic in the 
> > Google Groups "sage-devel" group. 
> > To unsubscribe from this topic, visit 
> > https://groups.google.com/d/topic/sage-devel/OBv5x1v3_6M/unsubscribe. 
> > To unsubscribe from this group and all its topics, send an email to 
> > sage-devel+...@googlegroups.com. 
> > To post to this group, send email to sage-...@googlegroups.com. 
> > Visit this group at http://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "sage-devel" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/sage-devel/OBv5x1v3_6M/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit 

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[nirmal]

I am looking forward to your update on how the process went. Thanks for 
your effort...

On Friday, September 25, 2015 at 11:46:48 AM UTC-7, Juan Luis Varona wrote:
>
> I have downlodaded 6.9.rc0 and I my computer is now compiling with xcode 7 
> on osx 11.10. 
>
> I will inform at the end of the process, 
>
> Juan Luis 
>
> > El 25 sept 2015, a las 17:12, John H Palmieri  > escribió: 
> > 
> > Please try the latest Sage prerelease (6.9.rc0, available here: 
> http://files.sagemath.org/devel/index.html) should build with Xcode 7, so 
> I hope it builds with OS X 10.11. 
> > 
> >   John 
> > 
> > 
> > On Friday, September 18, 2015 at 8:14:44 AM UTC-7, John H Palmieri 
> wrote: 
> > 
> > 
> > On Friday, September 18, 2015 at 2:01:24 AM UTC-7, Juan Luis Varona 
> wrote: 
> > Actually, xcode 7 were released yesterday. 
> > 
> > I can confirm that again sage 6.8 cannot be compiled in mac os x 10.11 
> with xcode 7. 
> > 
> > Juan Luis 
> > 
> > We are tracking build issues with Xcode 7 here: 
> http://trac.sagemath.org/ticket/19232. I hope fixing those will fix the 
> problems on OS X 10.11. 
> > 
> >   John 
> > 
> > 
> > > 
> > > Same problem, nobody find a solution ? If yes, please can you tell me 
> how ! 
> > > 
> > > Charles 
> > > 
> > > Le vendredi 11 septembre 2015 04:48:25 UTC+2, François a écrit : 
> > > Hum, that symbol is in libpython2.7.dylib, operator.so is not linked 
> to that library. 
> > > I am guessing it is supposed to be dlopen-ed from python which would 
> supply 
> > > the symbol. I suspect python will need patching. 
> > > Can you start python from a sage shell? 
> > > 
> > > François 
> > > 
> > > > On 11/09/2015, at 14:40, Juan Luis Varona  
> wrote: 
> > > > 
> > > > 
> > > >> El 11 sept 2015, a las 4:24, kcrisman  
> escribió: 
> > > >> 
> > > >> But, usually, new versions of osx can execute already compiled 
> versions of sage, and this does not happen this time. (I like to have 
> always the last version of osx in one of my computers, and I do not 
> remember this problem in the past.) 
> > > >> 
> > > >> 
> > > >> Yes, good point.  Can you give us exactly what kind of problems you 
> encounter with the 10.10 version on 10.11?  (If there are any message at 
> all.) 
> > > >> 
> > > > 
> > > > This is what appears in the Terminal using Sage-6.8.app (compiled 
> for osx 10.10) under osx 10.11: 
> > > > 
> > > > - 
> > > > 
> > > > Last login: Thu Sep 10 18:37:14 on ttys000 
> > > > AirTeXano:~ jvarona$ 
> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
> > > > Traceback (most recent call last): 
> > > >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
> line 7, in  
> > > >import argparse 
> > > >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
>  
> line 85, in  
> > > >import collections as _collections 
> > > >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
>  
> line 9, in  
> > > >from operator import itemgetter as _itemgetter, eq as _eq 
> > > > ImportError: 
> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
>  
> 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
> > > >  Referenced from: 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>  
>
> > > >  Expected in: flat namespace 
> > > > in 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>  
>
> > > > AirTeXano:~ jvarona$ 
> > > > 
> > > >  
> > > > 
> > > > Juan Luis 
> > > > 
> > > > 
> > > > -- 
> > > > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group. 
> > > > To unsubscribe from this group and stop receiving emails from it, 
> send an email to sage-devel+...@googlegroups.com. 
> > > > To post to this group, send email to sage-...@googlegroups.com. 
> > > > Visit this group at http://groups.google.com/group/sage-devel. 
> > > > For more options, visit https://groups.google.com/d/optout. 
> > > 
> > > 
> > > -- 
> > > You received this message because you are subscribed to a topic in the 
> Google Groups "sage-devel" group. 
> > > To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/sage-devel/OBv5x1v3_6M/unsubscribe. 
> > > To unsubscribe from this group and all its topics, send an email to 
> sage-devel+...@googlegroups.com. 
> > > To post to this group, send email to sage-...@googlegroups.com. 
> > > Visit this group at http://groups.google.com/group/sage-devel. 
> > > For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to a topic in the 
> Google Groups "sage-devel" group. 
> > To unsubscribe from this topic, visit 
> 

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

Actually, xcode 7 were released yesterday.

I can confirm that again sage 6.8 cannot be compiled in mac os x 10.11 with 
xcode 7.

Juan Luis

> 
> Same problem, nobody find a solution ? If yes, please can you tell me how !
> 
> Charles
> 
> Le vendredi 11 septembre 2015 04:48:25 UTC+2, François a écrit :
> Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to that 
> library. 
> I am guessing it is supposed to be dlopen-ed from python which would supply 
> the symbol. I suspect python will need patching. 
> Can you start python from a sage shell? 
> 
> François 
> 
> > On 11/09/2015, at 14:40, Juan Luis Varona  wrote: 
> > 
> > 
> >> El 11 sept 2015, a las 4:24, kcrisman  escribió: 
> >> 
> >> But, usually, new versions of osx can execute already compiled versions of 
> >> sage, and this does not happen this time. (I like to have always the last 
> >> version of osx in one of my computers, and I do not remember this problem 
> >> in the past.) 
> >> 
> >> 
> >> Yes, good point.  Can you give us exactly what kind of problems you 
> >> encounter with the 10.10 version on 10.11?  (If there are any message at 
> >> all.) 
> >> 
> > 
> > This is what appears in the Terminal using Sage-6.8.app (compiled for osx 
> > 10.10) under osx 10.11: 
> > 
> > - 
> > 
> > Last login: Thu Sep 10 18:37:14 on ttys000 
> > AirTeXano:~ jvarona$ 
> > '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
> > Traceback (most recent call last): 
> >  File 
> > "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
> > line 7, in  
> >import argparse 
> >  File 
> > "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
> >  line 85, in  
> >import collections as _collections 
> >  File 
> > "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
> >  line 9, in  
> >from operator import itemgetter as _itemgetter, eq as _eq 
> > ImportError: 
> > dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
> >  2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
> >  Referenced from: 
> > /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
> >  
> >  Expected in: flat namespace 
> > in 
> > /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
> >  
> > AirTeXano:~ jvarona$ 
> > 
> >  
> > 
> > Juan Luis 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google Groups 
> > "sage-devel" group. 
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to sage-devel+...@googlegroups.com. 
> > To post to this group, send email to sage-...@googlegroups.com. 
> > Visit this group at http://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "sage-devel" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/sage-devel/OBv5x1v3_6M/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[John H Palmieri]

On Friday, September 18, 2015 at 2:01:24 AM UTC-7, Juan Luis Varona wrote:
>
> Actually, xcode 7 were released yesterday. 
>
> I can confirm that again sage 6.8 cannot be compiled in mac os x 10.11 
> with xcode 7. 
>
> Juan Luis 
>

We are tracking build issues with Xcode 7 here: 
http://trac.sagemath.org/ticket/19232. I hope fixing those will fix the 
problems on OS X 10.11.

  John


> > 
> > Same problem, nobody find a solution ? If yes, please can you tell me 
> how ! 
> > 
> > Charles 
> > 
> > Le vendredi 11 septembre 2015 04:48:25 UTC+2, François a écrit : 
> > Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to 
> that library. 
> > I am guessing it is supposed to be dlopen-ed from python which would 
> supply 
> > the symbol. I suspect python will need patching. 
> > Can you start python from a sage shell? 
> > 
> > François 
> > 
> > > On 11/09/2015, at 14:40, Juan Luis Varona  
> wrote: 
> > > 
> > > 
> > >> El 11 sept 2015, a las 4:24, kcrisman  escribió: 
> > >> 
> > >> But, usually, new versions of osx can execute already compiled 
> versions of sage, and this does not happen this time. (I like to have 
> always the last version of osx in one of my computers, and I do not 
> remember this problem in the past.) 
> > >> 
> > >> 
> > >> Yes, good point.  Can you give us exactly what kind of problems you 
> encounter with the 10.10 version on 10.11?  (If there are any message at 
> all.) 
> > >> 
> > > 
> > > This is what appears in the Terminal using Sage-6.8.app (compiled for 
> osx 10.10) under osx 10.11: 
> > > 
> > > - 
> > > 
> > > Last login: Thu Sep 10 18:37:14 on ttys000 
> > > AirTeXano:~ jvarona$ 
> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
> > > Traceback (most recent call last): 
> > >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
> line 7, in  
> > >import argparse 
> > >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
>  
> line 85, in  
> > >import collections as _collections 
> > >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
>  
> line 9, in  
> > >from operator import itemgetter as _itemgetter, eq as _eq 
> > > ImportError: 
> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
>  
> 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
> > >  Referenced from: 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>  
>
> > >  Expected in: flat namespace 
> > > in 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>  
>
> > > AirTeXano:~ jvarona$ 
> > > 
> > >  
> > > 
> > > Juan Luis 
> > > 
> > > 
> > > -- 
> > > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group. 
> > > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-devel+...@googlegroups.com. 
> > > To post to this group, send email to sage-...@googlegroups.com. 
> > > Visit this group at http://groups.google.com/group/sage-devel. 
> > > For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to a topic in the 
> Google Groups "sage-devel" group. 
> > To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/sage-devel/OBv5x1v3_6M/unsubscribe. 
> > To unsubscribe from this group and all its topics, send an email to 
> sage-devel+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at http://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Charles Bourloud]

Same problem, nobody find a solution ? If yes, please can you tell me how !

Charles

Le vendredi 11 septembre 2015 04:48:25 UTC+2, François a écrit :
>
> Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to 
> that library. 
> I am guessing it is supposed to be dlopen-ed from python which would 
> supply 
> the symbol. I suspect python will need patching. 
> Can you start python from a sage shell? 
>
> François 
>
> > On 11/09/2015, at 14:40, Juan Luis Varona  > wrote: 
> > 
> > 
> >> El 11 sept 2015, a las 4:24, kcrisman  
> escribió: 
> >> 
> >> But, usually, new versions of osx can execute already compiled versions 
> of sage, and this does not happen this time. (I like to have always the 
> last version of osx in one of my computers, and I do not remember this 
> problem in the past.) 
> >> 
> >> 
> >> Yes, good point.  Can you give us exactly what kind of problems you 
> encounter with the 10.10 version on 10.11?  (If there are any message at 
> all.) 
> >> 
> > 
> > This is what appears in the Terminal using Sage-6.8.app (compiled for 
> osx 10.10) under osx 10.11: 
> > 
> > - 
> > 
> > Last login: Thu Sep 10 18:37:14 on ttys000 
> > AirTeXano:~ jvarona$ 
> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
> > Traceback (most recent call last): 
> >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
> line 7, in  
> >import argparse 
> >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
>  
> line 85, in  
> >import collections as _collections 
> >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
>  
> line 9, in  
> >from operator import itemgetter as _itemgetter, eq as _eq 
> > ImportError: 
> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
>  
> 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
> >  Referenced from: 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>  
>
> >  Expected in: flat namespace 
> > in 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>  
>
> > AirTeXano:~ jvarona$ 
> > 
> >  
> > 
> > Juan Luis 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-devel+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at http://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Volker Braun]

Looks like Apple kept the new behavior of DYLD_* environment variables and 
they are not passed down to launched interpreters. Hence sooner or later we 
crash with symbol not found as libraries can't be located. Really we should 
have switched to rpaths years ago, this would have saved so much pain. Also 
would explain why homebrew and friends didn't trip over that. Don't know of 
any workaround on 10.11 besides sourcing sage-env whenever a subshell is 
launched.



On Friday, September 11, 2015 at 4:48:25 AM UTC+2, François wrote:
>
> Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to 
> that library. 
> I am guessing it is supposed to be dlopen-ed from python which would 
> supply 
> the symbol. I suspect python will need patching. 
> Can you start python from a sage shell? 
>
> François 
>
> > On 11/09/2015, at 14:40, Juan Luis Varona  > wrote: 
> > 
> > 
> >> El 11 sept 2015, a las 4:24, kcrisman  
> escribió: 
> >> 
> >> But, usually, new versions of osx can execute already compiled versions 
> of sage, and this does not happen this time. (I like to have always the 
> last version of osx in one of my computers, and I do not remember this 
> problem in the past.) 
> >> 
> >> 
> >> Yes, good point.  Can you give us exactly what kind of problems you 
> encounter with the 10.10 version on 10.11?  (If there are any message at 
> all.) 
> >> 
> > 
> > This is what appears in the Terminal using Sage-6.8.app (compiled for 
> osx 10.10) under osx 10.11: 
> > 
> > - 
> > 
> > Last login: Thu Sep 10 18:37:14 on ttys000 
> > AirTeXano:~ jvarona$ 
> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook 
> > Traceback (most recent call last): 
> >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
> line 7, in  
> >import argparse 
> >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
>  
> line 85, in  
> >import collections as _collections 
> >  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
>  
> line 9, in  
> >from operator import itemgetter as _itemgetter, eq as _eq 
> > ImportError: 
> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
>  
> 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString 
> >  Referenced from: 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>  
>
> >  Expected in: flat namespace 
> > in 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>  
>
> > AirTeXano:~ jvarona$ 
> > 
> >  
> > 
> > Juan Luis 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-devel+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at http://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Francois Bissey]

Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to that 
library.
I am guessing it is supposed to be dlopen-ed from python which would supply
the symbol. I suspect python will need patching. 
Can you start python from a sage shell?

François

> On 11/09/2015, at 14:40, Juan Luis Varona  wrote:
> 
> 
>> El 11 sept 2015, a las 4:24, kcrisman  escribió:
>> 
>> But, usually, new versions of osx can execute already compiled versions of 
>> sage, and this does not happen this time. (I like to have always the last 
>> version of osx in one of my computers, and I do not remember this problem in 
>> the past.) 
>> 
>> 
>> Yes, good point.  Can you give us exactly what kind of problems you 
>> encounter with the 10.10 version on 10.11?  (If there are any message at 
>> all.) 
>> 
> 
> This is what appears in the Terminal using Sage-6.8.app (compiled for osx 
> 10.10) under osx 10.11:
> 
> -
> 
> Last login: Thu Sep 10 18:37:14 on ttys000
> AirTeXano:~ jvarona$ 
> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook
> Traceback (most recent call last):
>  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
> line 7, in 
>import argparse
>  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
>  line 85, in 
>import collections as _collections
>  File 
> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
>  line 9, in 
>from operator import itemgetter as _itemgetter, eq as _eq
> ImportError: 
> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
>  2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString
>  Referenced from: 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
>  Expected in: flat namespace
> in 
> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
> AirTeXano:~ jvarona$ 
> 
> 
> 
> Juan Luis
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

> El 11 sept 2015, a las 4:24, kcrisman  escribió:
> 
> But, usually, new versions of osx can execute already compiled versions of 
> sage, and this does not happen this time. (I like to have always the last 
> version of osx in one of my computers, and I do not remember this problem in 
> the past.) 
> 
> 
> Yes, good point.  Can you give us exactly what kind of problems you encounter 
> with the 10.10 version on 10.11?  (If there are any message at all.) 
> 

This is what appears in the Terminal using Sage-6.8.app (compiled for osx 
10.10) under osx 10.11:

-

Last login: Thu Sep 10 18:37:14 on ttys000
AirTeXano:~ jvarona$ '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage 
--notebook
Traceback (most recent call last):
  File 
"/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", 
line 7, in 
import argparse
  File 
"/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py",
 line 85, in 
import collections as _collections
  File 
"/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py",
 line 9, in 
from operator import itemgetter as _itemgetter, eq as _eq
ImportError: 
dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so,
 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString
  Referenced from: 
/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
  Expected in: flat namespace
 in 
/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so
AirTeXano:~ jvarona$ 



Juan Luis


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

> 
> Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to that 
> library.
> I am guessing it is supposed to be dlopen-ed from python which would supply
> the symbol. I suspect python will need patching. 
> Can you start python from a sage shell?
> 

But sage shell closes, so I cannot use it.

If, in the menu of the .app, I use “Terminal Sesion >> Misc. >> python”, I 
obtain this in Terminal:



Last login: Fri Sep 11 04:51:46 on ttys001
/Applications/Sage-6.8.app/Contents/Resources/sage/sage --python; exit
AirTeXano:~ jvarona$ /Applications/Sage-6.8.app/Contents/Resources/sage/sage 
--python; exit
Python 2.7.9 (default, Jul 28 2015, 17:58:38) 
[GCC 4.9.2] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> 

-


Juan Luis

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

A few days ago, Apple released mac osx 10.11 (El Capitan) public beta5.

As in previous public betas, I can confirm that sage 6.8 does not work.

I have tried again to compile it and it gives similar errors.
The entire log file is here (a 22.9 MB file):
https://dl.dropboxusercontent.com/u/8293746/log-compiling-sage68-osx10.11-beta5.txt

And this is what happens if you use ./sage:
--
Last login: Sat Aug 22 12:02:14 on ttys000
AirTeXano:~ jvarona$ /Applications/sage-6.8/sage ; exit;
┌┐
│ SageMath Version 6.8, Release Date: 2015-07-26 │
│ 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...

A crash report was automatically generated with the following information:
  - A verbatim copy of the crash traceback.
  - A copy of your input history during this session.
  - Data on your current Sage configuration.

It was left in the file named:
'/Users/jvarona/.sage/ipython-3.2.0/Sage_crash_report.txt'
If you can email this file to the developers, the information in it will 
help
them in understanding and correcting the problem.

You can mail it to: sage-support at sage-supp...@googlegroups.com
with the subject 'Sage Crash Report'.

If you want to do it now, the following command will work (under Unix):
mail -s 'Sage Crash Report' sage-supp...@googlegroups.com  
/Users/jvarona/.sage/ipython-3.2.0/Sage_crash_report.txt

To ensure accurate tracking of this issue, please file a report about it at:
http://trac.sagemath.org

Hit Enter to quit (your terminal may close):
--

Yours,

Juan Luis Varona

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Volker Braun]

Looks like everything is linked correctly. The following suggests that 
there is a bug in DYLD_LIBRARY_PATH handling in the OSX 10.11 betas:

https://forums.developer.apple.com/message/31148

Possibly thats an intentional change of the spec to fix the (still 
unpatched on all released OSX versions) DYLD_PRINT_TO_FILE root exploit.

In any case, please file a bug with Apple to bring this to their attention 
(even if you wont' get any useful information from them)



On Saturday, August 8, 2015 at 1:36:49 AM UTC+2, Juan Luis Varona wrote:


  El 8 ago 2015, a las 0:22, Volker Braun vbrau...@gmail.com 
 javascript: escribió: 
  
  sage -sh -c 'otool -L $SAGE_ROOT/local/lib/libsingular.dylib' 

 I’m not sure if this is what you want to check: 

 ./sage -sh -c 'otool -L $SAGE_ROOT/local/lib/libsingular.dylib’ 

 /Applications/sage-6.8/local/lib/libsingular.dylib: 
 libsingular.dylib (compatibility version 0.0.0, current version 
 0.0.0) 
 /Applications/sage-6.8/local/lib/libflint.dylib (compatibility 
 version 0.0.0, current version 0.0.0) 
 /Applications/sage-6.8/local/lib/libmpfr.4.dylib (compatibility 
 version 6.0.0, current version 6.2.0) 
 /Applications/sage-6.8/local/lib/libmpir.16.dylib (compatibility 
 version 17.0.0, current version 17.0.0) 
 /Applications/sage-6.8/local/lib/libntl.16.dylib (compatibility 
 version 17.0.0, current version 17.0.0) 
 /Applications/sage-6.8/local/lib/libreadline.6.dylib 
 (compatibility version 6.0.0, current version 6.3.0) 
 /Applications/sage-6.8/local/lib/libgmp.16.dylib (compatibility 
 version 17.0.0, current version 17.0.0) 
 /Applications/sage-6.8/local/lib/libstdc++.6.dylib (compatibility 
 version 7.0.0, current version 7.20.0) 
 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
 version 1225.0.0) 
 /Applications/sage-6.8/local/lib/libgcc_s.1.dylib (compatibility 
 version 1.0.0, current version 1.0.0) 




-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

 
 
 Looks like everything is linked correctly. The following suggests that there 
 is a bug in DYLD_LIBRARY_PATH handling in the OSX 10.11 betas:
 
 https://forums.developer.apple.com/message/31148
 
 Possibly thats an intentional change of the spec to fix the (still unpatched 
 on all released OSX versions) DYLD_PRINT_TO_FILE root exploit.
 
 In any case, please file a bug with Apple to bring this to their attention 
 (even if you wont' get any useful information from them)
 

Thanks. I have reported it to Apple using the Feedback Assistant for beta 
versions of macosx.

I will inform in this list if there are improvements in next betas of mac osx 
10.11 (El Capitan).

Yours,

Juan Luis Varona

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

 El 8 ago 2015, a las 0:22, Volker Braun vbraun.n...@gmail.com escribió:
 
 sage -sh -c 'otool -L $SAGE_ROOT/local/lib/libsingular.dylib'

I’m not sure if this is what you want to check:

./sage -sh -c 'otool -L $SAGE_ROOT/local/lib/libsingular.dylib’

/Applications/sage-6.8/local/lib/libsingular.dylib:
libsingular.dylib (compatibility version 0.0.0, current version 0.0.0)
/Applications/sage-6.8/local/lib/libflint.dylib (compatibility version 
0.0.0, current version 0.0.0)
/Applications/sage-6.8/local/lib/libmpfr.4.dylib (compatibility version 
6.0.0, current version 6.2.0)
/Applications/sage-6.8/local/lib/libmpir.16.dylib (compatibility 
version 17.0.0, current version 17.0.0)
/Applications/sage-6.8/local/lib/libntl.16.dylib (compatibility version 
17.0.0, current version 17.0.0)
/Applications/sage-6.8/local/lib/libreadline.6.dylib (compatibility 
version 6.0.0, current version 6.3.0)
/Applications/sage-6.8/local/lib/libgmp.16.dylib (compatibility version 
17.0.0, current version 17.0.0)
/Applications/sage-6.8/local/lib/libstdc++.6.dylib (compatibility 
version 7.0.0, current version 7.20.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 1225.0.0)
/Applications/sage-6.8/local/lib/libgcc_s.1.dylib (compatibility 
version 1.0.0, current version 1.0.0)


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Volker Braun]

On Friday, August 7, 2015 at 2:27:19 PM UTC+2, Juan Luis Varona wrote:

 sage -sh -c 'otool -L $SAGE_ROOT/local/lib/libsingular.dylib’


Your email client messed up the final backtick, it shoud be the same as all 
the other ones but you have a U+2019 there.

sage -sh -c 'otool -L $SAGE_ROOT/local/lib/libsingular.dylib'

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Francois Bissey]

All right. Do you have a file named
/Applications/sage-6.8/local/lib/libsingular.dylib?

François

 On 7/08/2015, at 23:32, Juan Luis Varona juanluis.var...@gmail.com wrote:
 
 I have tried to compile sage-6.8 (yesterday I wrote 2.6 instead of 6.8 by 
 mistake) under osx 10.11 beta4, again without sucess.
 
 This is the final error message:
 
 
 Unhandled SIGSEGV: A segmentation fault occurred in Sage.
 This probably occurred because a *compiled* component of Sage has a bug
 in it and is not properly wrapped with sig_on(), sig_off().
 Sage will now terminate.
 
 ./sage: line 134: 71464 Segmentation fault: 11  $SAGE_ROOT/src/bin/sage $@
 make[2]: *** [doc-html] Error 139
 make[1]: *** [all] Error 2
 
 real  1584m1.633s
 user  543m24.211s
 sys   61m11.615s
 ***
 Error building Sage.
 
 The following package(s) may have failed to build (not necessarily
 during this run of 'make all'):
 
 The build directory may contain configuration files and other potentially
 helpful information. WARNING: if you now run 'make' again, the build
 directory will, by default, be deleted. Set the environment variable
 SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
 
 make: *** [all] Error 1
 
 
 The entire log file is here (a 22.9 MB file):
 https://dl.dropboxusercontent.com/u/8293746/log-compiling-sage68-osx10.11-beta4.txt
 
 If I use ./sage, I get this message:
 ---
 Last login: Thu Aug  6 01:32:40 on ttys000
 AirTeXano:~ jvarona$ cd /Applications/sage-6.8 
 AirTeXano:sage-6.8 jvarona$ ./sage
 ┌┐
 │ SageMath Version 6.8, Release Date: 2015-07-26 │
 │ 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...
 
 A crash report was automatically generated with the following information:
   - A verbatim copy of the crash traceback.
   - A copy of your input history during this session.
   - Data on your current Sage configuration.
 
 It was left in the file named:
   '/Users/jvarona/.sage/ipython-3.2.0/Sage_crash_report.txt'
 If you can email this file to the developers, the information in it will help
 them in understanding and correcting the problem.
 
 You can mail it to: sage-support at sage-supp...@googlegroups.com
 with the subject 'Sage Crash Report'.
 
 If you want to do it now, the following command will work (under Unix):
 mail -s 'Sage Crash Report' sage-supp...@googlegroups.com  
 /Users/jvarona/.sage/ipython-3.2.0/Sage_crash_report.txt
 
 To ensure accurate tracking of this issue, please file a report about it at:
 http://trac.sagemath.org
 ---
 
 And this is the Sage_crash_report.txt file (32 KB file):
 https://dl.dropboxusercontent.com/u/8293746/Sage_crash_report.txt
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 sage-devel group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Volker Braun]

Also, whats the output of 

sage -sh -c 'otool -L $SAGE_ROOT/local/lib/libsingular.dylib'
sage -sh -c 'otool -L 
$SAGE_ROOT/local/lib/python2.7/site-packages/sage/matrix/matrix_mpolynomial_dense.so'



On Friday, August 7, 2015 at 1:56:39 PM UTC+2, Juan Luis Varona wrote:

  
  
  And what does 
  “file /Applications/sage-6.8/local/lib/libsingular.dylib” 
  says? 
  

 Yes, sure: 

 cd /Applications/sage-6.8/local/lib 

 ls -l 

 . . . 

 -rwxr-xr-x1 jvarona  staff8706256  6 ago 21:56 libsingular.dylib 

 . . . 




-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

 All right. Do you have a file named
 /Applications/sage-6.8/local/lib/libsingular.dylib?
 

Yes, it is a 8.7 MB file.

Yours,

Juan Luis

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Francois Bissey]

And what does 
“file /Applications/sage-6.8/local/lib/libsingular.dylib”
says?

François

 On 7/08/2015, at 23:43, Juan Luis Varona juanluis.var...@gmail.com wrote:
 
 
 
 All right. Do you have a file named
 /Applications/sage-6.8/local/lib/libsingular.dylib?
 
 
 Yes, it is a 8.7 MB file.
 
 Yours,
 
 Juan Luis
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 sage-devel group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

 
 
 I asked for the output of the “file” command. But I am not expecting anything 
 spectacular
 because what I thought about initially should have broken at compilation time.
 


Sorry, I was answering your previous message,

If I use

file /Applications/sage-6.8/local/lib/libsingular.dylib

I get

/Applications/sage-6.8/local/lib/libsingular.dylib: Mach-O 64-bit dynamically 
linked shared library x86_64

Juan Luis

 François
 
 On 7/08/2015, at 23:56, Juan Luis Varona juanluis.var...@gmail.com wrote:
 
 
 
 And what does 
 “file /Applications/sage-6.8/local/lib/libsingular.dylib”
 says?
 
 
 Yes, sure:
 
 cd /Applications/sage-6.8/local/lib
 
 ls -l
 
 . . . 
 
 -rwxr-xr-x1 jvarona  staff8706256  6 ago 21:56 libsingular.dylib
 
 . . .
 
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 sage-devel group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.
 
 -- 
 You received this message because you are subscribed to a topic in the Google 
 Groups sage-devel group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/sage-devel/OBv5x1v3_6M/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

 
 
 Also, whats the output of 
 
 sage -sh -c 'otool -L $SAGE_ROOT/local/lib/libsingular.dylib’


Nothing (only ).



 sage -sh -c 'otool -L 
 $SAGE_ROOT/local/lib/python2.7/site-packages/sage/matrix/matrix_mpolynomial_dense.so'
 

./sage -sh -c 'otool -L 
$SAGE_ROOT/local/lib/python2.7/site-packages/sage/matrix/matrix_mpolynomial_dense.so’

/Applications/sage-6.8/local/lib/python2.7/site-packages/sage/matrix/matrix_mpolynomial_dense.so:
libsingular.dylib (compatibility version 0.0.0, current version 0.0.0)
/Applications/sage-6.8/local/lib/libntl.16.dylib (compatibility version 
17.0.0, current version 17.0.0)
/Applications/sage-6.8/local/lib/libflint.dylib (compatibility version 
0.0.0, current version 0.0.0)
/Applications/sage-6.8/local/lib/libgmp.16.dylib (compatibility version 
17.0.0, current version 17.0.0)
/Applications/sage-6.8/local/lib/libgmpxx.8.dylib (compatibility 
version 9.0.0, current version 9.0.0)
/Applications/sage-6.8/local/lib/libreadline.6.dylib (compatibility 
version 6.0.0, current version 6.3.0)
/Applications/sage-6.8/local/lib/libstdc++.6.dylib (compatibility 
version 7.0.0, current version 7.20.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 1225.0.0)
/Applications/sage-6.8/local/lib/libgcc_s.1.dylib (compatibility 
version 1.0.0, current version 1.0.0)




-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Francois Bissey]

I asked for the output of the “file” command. But I am not expecting anything 
spectacular
because what I thought about initially should have broken at compilation time.

François

 On 7/08/2015, at 23:56, Juan Luis Varona juanluis.var...@gmail.com wrote:
 
 
 
 And what does 
 “file /Applications/sage-6.8/local/lib/libsingular.dylib”
 says?
 
 
 Yes, sure:
 
 cd /Applications/sage-6.8/local/lib
 
 ls -l
 
 . . . 
 
 -rwxr-xr-x1 jvarona  staff8706256  6 ago 21:56 libsingular.dylib
 
 . . .
 
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 sage-devel group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Sage in Mac OSX 11.11 (El Capitan)

[Juan Luis Varona]

I have try to install sage (the current stable version 6.7) in Mac OSX 
11.11 (El Capitan), public beta (the final version will be available after 
the summer).

I have tried with both
*sage-6.7-x86_64-Darwin-OSX_10.10_x86_64.dmg 
ftp://ftp.fu-berlin.de/unix/misc/sage/osx/sage-6.7-x86_64-Darwin-OSX_10.10_x86_64.dmg*
and
*sage-6.7-x86_64-Darwin-OSX_10.10_x86_64-app.dmg 
ftp://ftp.fu-berlin.de/unix/misc/sage/osx/sage-6.7-x86_64-Darwin-OSX_10.10_x86_64-app.dmg*
without success.

None of them can be used due to an error. I have not found any information 
about it in any sage page, so I report it.
This is the error message:

Last login: Tue Jul 14 02:29:58 on ttys001
AirTeXano:~ jvarona$ /Applications/sage/sage ; exit;
┌┐
│ SageMath Version 6.7, Release Date: 2015-05-17 │
│ Type notebook() for the browser-based notebook interface.│
│ Type help() for help.│
└┘
The Sage installation tree has moved
from /Users/buildslave-sage/slave/sage_git/build
  to /Applications/sage
Updating various hardcoded paths...
(Please wait at most a few minutes.)
DO NOT INTERRUPT THIS.
Done updating paths.
Traceback (most recent call last):
  File /Applications/sage/src/bin/sage-ipython, line 7, in module
from sage.repl.interpreter import SageTerminalApp
  File 
/Applications/sage/local/lib/python2.7/site-packages/sage/__init__.py, 
line 3, in module
from sage.repl.ipython_extension import load_ipython_extension
  File 
/Applications/sage/local/lib/python2.7/site-packages/sage/repl/ipython_extension.py,
 
line 59, in module
from IPython.core.magic import Magics, magics_class, line_magic
  File 
/Applications/sage/local/lib/python2.7/site-packages/IPython/__init__.py, 
line 45, in module
from .config.loader import Config
  File 
/Applications/sage/local/lib/python2.7/site-packages/IPython/config/__init__.py,
 
line 6, in module
from .application import *
  File 
/Applications/sage/local/lib/python2.7/site-packages/IPython/config/application.py,
 
line 9, in module
import json
  File /Applications/sage/local/lib/python/json/__init__.py, line 108, in 
module
from .decoder import JSONDecoder
  File /Applications/sage/local/lib/python/json/decoder.py, line 5, in 
module
import struct
  File /Applications/sage/local/lib/python/struct.py, line 1, in module
from _struct import *
ImportError: 
dlopen(/Applications/sage/local/lib/python2.7/lib-dynload/_struct.so, 2): 
Symbol not found: _PyUnicodeUCS4_AsEncodedString
  Referenced from: 
/Applications/sage/local/lib/python2.7/lib-dynload/_struct.so
  Expected in: flat namespace
 in /Applications/sage/local/lib/python2.7/lib-dynload/_struct.so
logout
Saving session...completed.

[Proceso completado]



-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.