Re: [sage-devel] El Capitan SIGSEGV upon compiling sage 6.9

2015-10-22 Thread Volker Braun
6.10.beta1 On Thursday, October 22, 2015 at 8:31:12 PM UTC+2, Christian Nassau wrote: > > You need at least 6.10.beta0 to compile on OSX10.11 - your issues seem > similar to those of #19370 where this was fixed. > -- You received this message because you are subscribed to the Google Groups "sa

Re: [sage-devel] El Capitan SIGSEGV upon compiling sage 6.9

2015-10-22 Thread Christian Nassau
Hi Alejandro, You need at least 6.10.beta0 to compile on OSX10.11 - your issues seem similar to those of #19370 where this was fixed. HTH, Christian On 22.10.2015 18:52, Alejandro Erickson wrote: I get an error that I don't see much information about when compiling on El Capitan. The short

Re: [sage-devel] el capitan statement

2015-10-07 Thread David Roe
Do you want to mention the possibility of disabling system integrity protection, or are you purposefully avoiding that option? David On Wed, Oct 7, 2015 at 12:38 PM, William Stein wrote: > Hi, > > We need to post a statement on the Sagemath.org website about the El > Capitan os x 10.11 situation

[sage-devel] el capitan statement

2015-10-07 Thread William Stein
Hi, We need to post a statement on the Sagemath.org website about the El Capitan os x 10.11 situation, since I'm getting (or will be getting) emails "left and right" from people freaking out about this. Here's one answer -- how could it be reworded to be right? --- Hi, As far as I know, there is

Re: [sage-devel] el capitan

2015-10-07 Thread Francois Bissey
Yes R need to be checked over but it will have to be more elaborate than the ad hoc things I put for the others. R also suffers from http://trac.sagemath.org/ticket/18254 on OS X 10.11. The fix was only applied on 10.10 and I think that was not well thought out. It won’t get better without somethin

Re: [sage-devel] el capitan

2015-10-06 Thread Francois Bissey
I now have a segfault 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. But I think libsingular may be the main point of failure thr

[sage-devel] el capitan

2015-10-06 Thread François Bissey
Hi all OS X sufferers, I have been working about adding rpath from gcc but it turns out it may not be the problem or possibly not the only problem. For some time there has been a known issue that a number of components shipped with sage do not set up proper "install_name" for their libraries. li