| 1 |
> Hey Guys, |
| 2 |
> |
| 3 |
> Perhaps I shouldn't have sage-clib with use=mpir enabled, but if I do |
| 4 |
> the |
| 5 |
> sage-clib-4.4.4-importenv.patch fails because the first hunk in |
| 6 |
> sage-clib-4.4.3-replace-gmp-with-mpir.patch has already overwritten gmp |
| 7 |
> with mpir. I'm not sure |
| 8 |
> but perhaps the sage-clib-4.4.3-replace-gmp-with-mpir.patch should also |
| 9 |
> have the environment stuff that's in the first hunk of |
| 10 |
> sage-clib-4.4.4-importenv.patch. |
| 11 |
> |
| 12 |
Hi Steve, |
| 13 |
|
| 14 |
we probably should disable that flag until we have a number of kinks sorted |
| 15 |
out.... |
| 16 |
Patches and dependencies - in theory we would need to enforce pari[mpir=] |
| 17 |
and ntl[mpir=]. I will look at these patches later, after I have gone through |
| 18 |
my other priorities: |
| 19 |
*ATLAS independence [hoping it will hit the overlay in a few hours] |
| 20 |
*system singular which has to be read for sage-4.5 |
| 21 |
|
| 22 |
> |
| 23 |
> P.S. |
| 24 |
> The parallel build of sage-core now only takes several minutes here |
| 25 |
> with 4 cpu cores. Of course ccache was enabled so a fresh build would |
| 26 |
> take a bit longer. |
| 27 |
Yeah! With real CPUs that must be awesome. The cython calls used to be |
| 28 |
serial and use only one CPU, ccache doesn't do anything about those, so |
| 29 |
you should have a real benefit on that end. Then the compilation will be |
| 30 |
parallelized which is good as well. |
| 31 |
|
| 32 |
Francois |
Archives