el capitan

422 views
Skip to first unread message

François Bissey

unread,
Oct 6, 2015, 10:24:45 PM10/6/15
to sage-...@googlegroups.com
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. libsingular is one such library.

The install_name acts as an hint on where to load a library when
linking. It looks like El Capitan has become more strict about
this.

Concretely what to try:
From SAGE_ROOT:
install_name_tool -id ${SAGE_ROOT}/lib/libsingular.dylib
local/lib/libsingular.dylib
Replace ${SAGE_ROOT} explicitly by its value. Once this is done
sage itself needs to be rebuilt.
./sage -ba

There may be more of those lurking. I am rebuilding now.

Francois

Francois Bissey

unread,
Oct 6, 2015, 10:55:23 PM10/6/15
to sage-...@googlegroups.com
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 through other components.

François
> --
> 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.

kcrisman

unread,
Oct 7, 2015, 2:40:20 AM10/7/15
to sage-devel
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. libsingular is one such library.


R as well? 

Francois Bissey

unread,
Oct 7, 2015, 2:52:19 AM10/7/15
to sage-...@googlegroups.com
Haven’t checked yet but so far I have dealt with libsingular, zn_poly and
cliquer.

For some reason git doesn’t want to build in my current run.

Do we have a ticket for El Capitan where I can push things for
other brave people?

François

Francois Bissey

unread,
Oct 7, 2015, 7:09:35 AM10/7/15
to sage-...@googlegroups.com
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 something radical happening.

The fix for openssl for git 2.3.0 is ineffective and I had to replace it
with something a bit less subtle.

So I don’t have the crash because of libraries that cannot be found
anymore but I have this segfault and I will have to rebuild again with
debugging enabled. I am including the patch with the state of my branch
so other people can try it while I catch some zzzz.

François
el_capitan.patch
ATT00001.txt
Reply all
Reply to author
Forward
0 new messages