Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Jeroen Demeyer
This has been the default for a long time now, there is no need to add it explicitly: On 2016-05-09 00:17, Volker Braun wrote: export SAGE_PARALLEL_SPKG_BUILD=yes -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this gr

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Thierry
On Sun, May 08, 2016 at 03:17:44PM -0700, Volker Braun wrote: > The intended way to customize this is to create your own sage-debian.yaml > where you modify the build instructions as you want them: > > build: | > export SAGE_FAT_BINARY=yes > export SAGE_PARALLEL_SPKG_BUILD=yes > expor

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Thierry
On Sun, May 08, 2016 at 03:02:19PM -0700, William Stein wrote: > On Sunday, May 8, 2016, Thierry wrote: > > > On Sun, May 08, 2016 at 02:53:58PM -0700, William Stein wrote: > > > On Sunday, May 8, 2016, Thierry > > wrote: > > > > > > > Hi, > > > > > > > > i have to witness that for Sage Debian L

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Volker Braun
The intended way to customize this is to create your own sage-debian.yaml where you modify the build instructions as you want them: build: | export SAGE_FAT_BINARY=yes export SAGE_PARALLEL_SPKG_BUILD=yes export MAKE='make -j{ncpu}' make git gc --aggressive --prune=now Then "

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Thierry
On Sun, May 08, 2016 at 10:08:14PM +0200, Thierry wrote: > On Sun, May 08, 2016 at 02:53:58PM -0700, William Stein wrote: > > On Sunday, May 8, 2016, Thierry wrote: > > > > > Hi, > > > > > > i have to witness that for Sage Debian Live, i currently have to fork the > > > behaviour of "sage -bdist"

[sage-devel] Re: Building binaries...

2016-05-08 Thread William Stein
On Sunday, May 8, 2016, Thierry wrote: > On Sun, May 08, 2016 at 02:53:58PM -0700, William Stein wrote: > > On Sunday, May 8, 2016, Thierry > wrote: > > > > > Hi, > > > > > > i have to witness that for Sage Debian Live, i currently have to fork > the > > > behaviour of "sage -bdist" to continue

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Thierry
On Sun, May 08, 2016 at 02:53:58PM -0700, William Stein wrote: > On Sunday, May 8, 2016, Thierry wrote: > > > Hi, > > > > i have to witness that for Sage Debian Live, i currently have to fork the > > behaviour of "sage -bdist" to continue maintain the live. Indeed, it is > > > Where is your for

[sage-devel] Re: Building binaries...

2016-05-08 Thread William Stein
On Sunday, May 8, 2016, Thierry wrote: > Hi, > > i have to witness that for Sage Debian Live, i currently have to fork the > behaviour of "sage -bdist" to continue maintain the live. Indeed, it is Where is your fork? > still not clear to me how to use the new binary-pkg to package a > custo

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Thierry
Hi, i have to witness that for Sage Debian Live, i currently have to fork the behaviour of "sage -bdist" to continue maintain the live. Indeed, it is still not clear to me how to use the new binary-pkg to package a customized sage install. To let the key be self-contained, i install most optional

[sage-devel] Re: Building binaries...

2016-05-08 Thread William Stein
On Sunday, May 8, 2016, Volker Braun wrote: > On Sunday, May 8, 2016 at 6:19:43 AM UTC+2, William wrote: >> >> which is 593M. >> > > Sounds a bit too small, the buildbot binaries are always about twice that. > Ok that's good to know and explains why the binaries didn't work. I'll try building

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Volker Braun
On Sunday, May 8, 2016 at 6:19:17 PM UTC+2, William wrote: > > > b) modifying a shared library in the destination /tmp/sage-dev/ has no > > effect until you relink the binary/cython extension that uses it. > > Can you elaborate on b slightly? I don't understand for sure. > Say, you go to the

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread William Stein
On Sun, May 8, 2016 at 1:34 AM, Volker Braun wrote: > On Sunday, May 8, 2016 at 6:54:38 AM UTC+2, William wrote: >> >> time rsync -axH /projects/sage/sage-dev/ sage-dev/ > > > Thats fine. The only caveat is that rpaths are still pointing to the source. > Therefore > a) the copy stops working if y

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Volker Braun
On Sunday, May 8, 2016 at 6:54:38 AM UTC+2, William wrote: > > time rsync -axH /projects/sage/sage-dev/ sage-dev/ > Thats fine. The only caveat is that rpaths are still pointing to the source. Therefore a) the copy stops working if you delete /projects/sage/sage-dev/ b) modifying a shared libra

Re: [sage-devel] Re: Building binaries...

2016-05-08 Thread Volker Braun
On Sunday, May 8, 2016 at 6:19:43 AM UTC+2, William wrote: > > which is 593M. > Sounds a bit too small, the buildbot binaries are always about twice that. instantly prints out massive screenfulls of information -- with no > warning, and no indicator that hitting control+c is a bad idea. Wait,