Am 2016-09-11 um 04:01 schrieb Daniel Krenn:
> On 2016-09-10 18:36, Johan S. H. Rosenkilde wrote:
>> Without this or a similar schema, working on multiple tickets becomes
>> absolutely unbearable for me due to compilation time. How do you guys
>> cope with that?
>
> Having a version of each
Paul Masson wrote:
>> But a Sage-installed ccache should also "just work".
>
> Jeroen, could you elaborate on this? How does one use ccache most simply
> with Sage?
./sage -i ccache
That's all, unless you want to configure it differently.
(After installation, see local/etc/ccache.conf.)
> But a Sage-installed ccache should also "just work".
Jeroen, could you elaborate on this? How does one use ccache most simply
with Sage?
If this is currently the only way to speed up rebuilding when switching
between branches, then I would like to add a concise description to the
Johan S. H. Rosenkilde wrote:
> I seriously think a lot of beginners are struggling with compilation
> time when working with Sage, inadvertently jumping a lot between
> releases. Apparently, my workflow is not popular, but could we still
> add something to the Development manual to help people?
Johan S. H. Rosenkilde wrote:
>
> leif writes:
>> Well, probably it's just me, but I always (also) review tickets on trac
>> (i.e., via what git-o-lite gives); the whole branch, but also each
>> individual commit. You just need a browser to do so.
>
> I use git-o-lite a lot too, but often
leif writes:
> Well, probably it's just me, but I always (also) review tickets on trac
> (i.e., via what git-o-lite gives); the whole branch, but also each
> individual commit. You just need a browser to do so.
I use git-o-lite a lot too, but often switch back to my Emacs and git
log using
On 2016-09-11 10:48, Johan S. H. Rosenkilde wrote:
Jeroen Demeyer writes:
https://ccache.samba.org/
And I forgot to mention that I have 2 complete Sage installation trees
so I can let one compile while I use the other.
Thanks, that's useful. Do you need any special setup or care for making
Jeroen Demeyer writes:
>> https://ccache.samba.org/
>
> And I forgot to mention that I have 2 complete Sage installation trees
> so I can let one compile while I use the other.
Thanks, that's useful. Do you need any special setup or care for making
it work in the complicated Sage compilation
On 2016-09-11 08:43, Jeroen Demeyer wrote:
On 2016-09-10 18:36, Johan S. H. Rosenkilde wrote:
How do you guys cope with that?
https://en.wikipedia.org/wiki/Patience
https://ccache.samba.org/
And I forgot to mention that I have 2 complete Sage installation trees
so I can let one compile
On 2016-09-10 18:36, Johan S. H. Rosenkilde wrote:
How do you guys cope with that?
https://en.wikipedia.org/wiki/Patience
https://ccache.samba.org/
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
On 2016-09-10 18:36, Johan S. H. Rosenkilde wrote:
> Without this or a similar schema, working on multiple tickets becomes
> absolutely unbearable for me due to compilation time. How do you guys
> cope with that?
Having a version of each stable/rc/beta SageMath in a separate
directory. Every now
Johan S. H. Rosenkilde wrote:
> leif writes:
>>> But if you want to actually make changes then this creates a new merge
>>> commit which furthermore is against the conventional order (where the
>>> feature branch is the first parent). So it makes the commit history harder
>>> to understand.
>>
On Saturday, September 10, 2016 at 9:14:08 AM UTC-7, leif wrote:
>
> For new branches, I think it's best to base them on the last *stable*
> release (i.e., check out master before creating the new branch), unless
> you really need fixes from later betas, or it's clear (or likely) that
> you'd
leif writes:
>> But if you want to actually make changes then this creates a new merge
>> commit which furthermore is against the conventional order (where the
>> feature branch is the first parent). So it makes the commit history harder
>> to understand.
>
> I'd rather say "impossible", or
The upstream bugs are still open:
https://github.com/cython/cython/issues?q=is%3Aissue%20is%3Aopen%20cycache
On Saturday, September 10, 2016 at 5:36:53 PM UTC+2, leif wrote:
>
> Volker Braun wrote:
> > There is cycache, but its currently disabled in Sage as we ran into some
> > bugs.
>
>
Johan S. H. Rosenkilde wrote:
> Volker Braun writes:
>
>> Thats ok for reviewing tickets, and implemented as "git trac try
>> ".
>
> OK. I had a chat with Thierry Monteil and we agreed there were some
> subtle differences I don't remember - but I'll take a look at "git trac
> try".
>
>> But
Volker Braun wrote:
> There is cycache, but its currently disabled in Sage as we ran into some
> bugs.
Well, since quite a while though, isn't it?
Did anyone recently check whether the issue still exists, or could you
give a pointer?
-leif
> On Saturday, September 10, 2016 at 12:20:54 AM
Jeroen Demeyer wrote:
> On 2016-09-09 12:56, Marco Cognetta wrote:
>> It has happened to me where I build sage, turn off my computer, turn it
>> back on, and build it again. There were no changes made in the meantime
>> and it still does the cythonizing step.
>
> Are you really sure that you
Jeroen Demeyer wrote:
> On 2016-09-09 08:43, Marco Cognetta wrote:
>> However, if I change to a
>> new branch that has no changes which would necessitate recythonizing
>> code, it will go through the cythonizing step again.
>
> What makes you think that there are no changes which would
19 matches
Mail list logo
