| 1 |
Hi Steve, |
| 2 |
|
| 3 |
thanks for reporting - I just pushed my latest changes which should fix the |
| 4 |
problem. Re-emerging sage-base should create the needed directories; sage-core |
| 5 |
contains your proposed patch. |
| 6 |
|
| 7 |
Christopher |
| 8 |
|
| 9 |
On Sunday 18 April 2010 07:32:05 Steven Trogdon wrote: |
| 10 |
> Christopher, |
| 11 |
> |
| 12 |
> The follow probably only applies to amd64. Sage will not install with the |
| 13 |
> subject ebuilds. The |
| 14 |
> "sage -c" during postinstall fails because the files |
| 15 |
> |
| 16 |
> /opt/sage/local/lib/sage-flag.txt |
| 17 |
> /opt/sage/local/lib/sage-current-location.txt |
| 18 |
> |
| 19 |
> cannot be written since /opt/sage/local/lib doesn't exit. I suppose the |
| 20 |
> files are needed. One can create the symlink lib -> lib64 if lib is needed |
| 21 |
> or whatever. Even if this is fixed "sage -c" fails because the amd64-hack |
| 22 |
> patch does't take. The spkg-install is bypassed with the sage-core ebuild. |
| 23 |
> I tried a variety of things to get Sage to install and adding |
| 24 |
> |
| 25 |
> append-flags -fno-strict-aliasing |
| 26 |
> |
| 27 |
> to the sage-core ebuild works here. I'm not sure of the impact on ~x86 or |
| 28 |
> ~pcc. |
| 29 |
> |
| 30 |
> Steve |
Archives