> Christopher, > > The follow probably only applies to amd64. Sage will not install with the > subject ebuilds. The > "sage -c" during postinstall fails because the files > > /opt/sage/local/lib/sage-flag.txt > /opt/sage/local/lib/sage-current-location.txt > > cannot be written since /opt/sage/local/lib doesn't exit. I suppose the > files are needed. One can create the symlink lib -> lib64 if lib is needed > or whatever. Even if this is fixed "sage -c" fails because the amd64-hack > patch does't take. The spkg-install is bypassed with the sage-core ebuild. > I tried a variety of things to get Sage to install and adding > > append-flags -fno-strict-aliasing > > to the sage-core ebuild works here. I'm not sure of the impact on ~x86 or > ~pcc. > Hi Steve,
thanks for the report. We need to patch the sage-location script. I would prefer to get rid of it actually but that may not be possible in the short term. The problem is right there at the top of the script: #!/usr/bin/env python import os, sys SAGE_ROOT = os.environ['SAGE_ROOT'] location_file = '%s/local/lib/sage-current-location.txt'%SAGE_ROOT flags_file = '%s/local/lib/sage-flags.txt'%SAGE_ROOT ----------------- We put things nicely into lib/lib64 now, so it is a problem. We may have to grep all the sage scripts for other offenders. I am not sure I can post a fix straight away: sed -i "s:local/lib/sage:local/$(get_libdir)/sage:g" sage-location in src_prepare should do the trick. Francois
