On Wed, Jan 9, 2013 at 2:46 PM, Robert Bradshaw
<rober...@math.washington.edu> wrote:
> On Wed, Jan 9, 2013 at 2:07 PM, R. Andrew Ohana <andrew.oh...@gmail.com> 
> wrote:
>> On Wed, Jan 9, 2013 at 2:00 PM, John Cremona <john.crem...@gmail.com> wrote:
>>>
>>> I installed ccache (on ubuntu) but did no symlinking -- instead I
>>> compiled eclib after (re)configuring using CXX='ccache gcc'
>>> ./configure.  The result was a 320MB ~/.ccache, and a *very* quick
>>> recompile after "make clean; make".
>>
>>
>> Unfortunately not all spkgs play nicely when gcc/g++ is an argument of
>> ccache (hence the need for an actual symlink).
>
> That can be done internally, right?
>
>>> On 9 January 2013 21:39, Robert Bradshaw <rober...@math.washington.edu>
>>> wrote:
>>> > Is 1G an acceptable default for Sage? (I.e is it sufficient for a full
>>> > Sage build (plus some branching) plus a fair amount of other stuff?
>>> > This is my only concern, otherwise I'd say option (1) is the best.
>>> >
>>
>>
>> When I initially created the spkg, I found that building sage with clean
>> ccache would fill about 2.3-2.5G. That was the main reason I went with (2),
>> but I don't have any strong opinion on the matter.
>
> So, if the system default is 1G and we share .ccache, we'll loose over
> half our artifacts every time ccache is invoked (outside of our
> control at least). That seems really bad, so now I'm favoring (3).

I take this back--for the "average" developer 1G would still be
useful, I would imagine that most branch switches would not involve
many spkgs and a lot of code change. Someone who re-builds from
scratch quite often (rather than upgrading) would be served by a
bigger cache, but they're not (hopefully, in the new workflow) a
typical developer. In this case I saw we go for option (1).

There's still the issue of avoiding $HOME if it's an NFS mount, etc.

- Robert

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.


Reply via email to