On Sat, 21 Jun 2008 17:06:41 +0200
Martin Tournoij <[EMAIL PROTECTED]> wrote:
> As a sidenote, AFAIK cons and scons are not related...
They are distantly related.
The Software Carpentry project was looking for a make replacement. Cons
was not eligible because it (and thus its configuration) w
On Sat, 21 Jun 2008 10:25:41 -0500, Alex Kozlov <[EMAIL PROTECTED]> wrote:
On Sat, Jun 21, 2008 at 01:32:20AM +0100, RW wrote:
On Wed, 18 Jun 2008 23:27:16 +0200
Martin Tournoij <[EMAIL PROTECTED]> wrote:
> There are some ports which refuse to compile with ccache, these all
> seem to be proje
On Sat, Jun 21, 2008 at 01:32:20AM +0100, RW wrote:
> On Wed, 18 Jun 2008 23:27:16 +0200
> Martin Tournoij <[EMAIL PROTECTED]> wrote:
>
>
> > There are some ports which refuse to compile with ccache, these all
> > seem to be projects which use scons, unlike make, scons does not copy
> > the user'
On Sat, Jun 21, 2008 at 01:32:20AM +0100, RW wrote:
> On Wed, 18 Jun 2008 23:27:16 +0200
> Martin Tournoij <[EMAIL PROTECTED]> wrote:
>
> > There are some ports which refuse to compile with ccache, these all
> > seem to be projects which use scons, unlike make, scons does not copy
> > the user's e
On Wed, 18 Jun 2008 23:27:16 +0200
Martin Tournoij <[EMAIL PROTECTED]> wrote:
> There are some ports which refuse to compile with ccache, these all
> seem to be projects which use scons, unlike make, scons does not copy
> the user's environment automatically, and the required environment
> variab
On Wed, Jun 18, 2008 at 10:51:54PM +1000, Edwin Groothuis wrote:
> Hello,
>
> Recently I've started to use devel/ccache again (sometimes it takes
> a while before you understand how it works) and it works pretty
> well, except for some ports which can't be build with it. For example
> devel/cmake.
On Wed, 18 Jun 2008 22:06:21 +0300
Alex Kozlov <[EMAIL PROTECTED]> wrote:
> In typical case check for size and mtime is enough.
It's not really a question of good enough, if you use the mtime of
the driver on all builds, then *every* time you rebuild the compiler,
you invaldate all the cache obj
On Wed, Jun 18, 2008 at 07:05:36PM +0100, RW wrote:
> On Wed, 18 Jun 2008 20:23:52 +0300
> Alex Kozlov <[EMAIL PROTECTED]> wrote:
> > This is not luck. To think more about this, CCACHE_HASH_COMPILER
> > and CCACHE_NOHASH_SIZE_MTIME is two method for the same.
> > hash size and mtime is lightweight
On Wed, 18 Jun 2008 20:23:52 +0300
Alex Kozlov <[EMAIL PROTECTED]> wrote:
> This is not luck. To think more about this, CCACHE_HASH_COMPILER
> and CCACHE_NOHASH_SIZE_MTIME is two method for the same.
> hash size and mtime is lightweight and CCACHE_HASH_COMPILER
> is more heavy.
It's negligible,
On Wed, Jun 18, 2008 at 06:44:36PM +0200, Alex Dupre wrote:
>> Problem in make buildworld case is not compiler name.
> hash_file() doesn't hash the file name :-)
Yes, sorry. s/name/identity/. In other words this check to make
sure that obj was created the same compiler.
> You are lucky that CCACHE
On Wed, Jun 18, 2008 at 06:44:36PM +0200, Alex Dupre wrote:
> Alex Kozlov wrote:
> > Problem in make buildworld case is not compiler name.
> hash_file() doesn't hash the file name :-)
Yes, sorry. s/name/identity/. In other world this check to make
sure that obj was created the same compiler.
> You
Alex Kozlov wrote:
> Problem in make buildworld case is not compiler name.
hash_file() doesn't hash the file name :-)
You are lucky that CCACHE_HASH_COMPILER is checked before
CCACHE_NOHASH_SIZE_MTIME.
--
Ale
___
freebsd-ports@freebsd.org mailing list
On Wed, 18 Jun 2008 18:26:14 +0300
Alex Kozlov <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 05:05:42PM +0200, Alex Dupre wrote:
> > Alex Kozlov ha scritto:
> > > Don't use it for building ports. Actualy it's not necessary even
> > > for make buildworld.
> >
> > It's necessary if you don't
On Wed, Jun 18, 2008 at 05:48:38PM +0200, Alex Dupre wrote:
> Alex Kozlov ha scritto:
> >> It's necessary if you don't want to use ccache only for 1% of the
> >> buildworld process.
> > I use CCACHE_NOHASH_SIZE_MTIME:
>
> "It's not necessary to use CCACHE_HASH_COMPILER" != "I use
> CCACHE_NOHASH
Alex Kozlov ha scritto:
It's necessary if you don't want to use ccache only for 1% of the
buildworld process.
I use CCACHE_NOHASH_SIZE_MTIME:
"It's not necessary to use CCACHE_HASH_COMPILER" != "I use
CCACHE_NOHASH_SIZE_MTIME, so every compiler I use I will get always the
same result."
--
On Wed, Jun 18, 2008 at 05:05:42PM +0200, Alex Dupre wrote:
> Alex Kozlov ha scritto:
> > Don't use it for building ports. Actualy it's not necessary even for
> > make buildworld.
>
> It's necessary if you don't want to use ccache only for 1% of the
> buildworld process.
I use CCACHE_NOHASH_SIZE_
Alex Kozlov ha scritto:
Don't use it for building ports. Actualy it's not necessary even for
make buildworld.
It's necessary if you don't want to use ccache only for 1% of the
buildworld process.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing
On Wed, Jun 18, 2008 at 11:16:42PM +1000, Edwin Groothuis wrote:
> On Wed, Jun 18, 2008 at 03:01:58PM +0200, Alex Dupre wrote:
> > Edwin Groothuis ha scritto:
> > >Recently I've started to use devel/ccache again (sometimes it takes
> > >a while before you understand how it works) and it works prett
Edwin Groothuis ha scritto:
===> Configuring for cmake-2.6.0
-
CMake 2.6-0, Copyright (c) 2007 Kitware, Inc., Insight Consortium
C compiler on this system is: /usr/local/libexec/ccache/world-cc -O2 -fno-strict-aliasing -pipe
C++ compiler on this syste
Edwin Groothuis ha scritto:
Recently I've started to use devel/ccache again (sometimes it takes
a while before you understand how it works) and it works pretty
well, except for some ports which can't be build with it. For example
devel/cmake.
I use ccache everywhere (world and ports) and I neve
On Wed, Jun 18, 2008 at 03:11:43PM +0200, Alex Dupre wrote:
> Edwin Groothuis ha scritto:
> >Unfortunately /etc/make.conf is read before the ports Makefile is
> >read, so this in /etc/make.conf isn't going to work anymore:
> >
> > .if !defined(NO_CCACHE)
> > CC=/usr/local/libexec/ccache/cc
Edwin Groothuis ha scritto:
Unfortunately /etc/make.conf is read before the ports Makefile is
read, so this in /etc/make.conf isn't going to work anymore:
.if !defined(NO_CCACHE)
CC=/usr/local/libexec/ccache/cc
CXX=/usr/local/libexec/ccache/c++
CPP=/usr/local/libe
On Wed, Jun 18, 2008 at 03:01:58PM +0200, Alex Dupre wrote:
> Edwin Groothuis ha scritto:
> >Recently I've started to use devel/ccache again (sometimes it takes
> >a while before you understand how it works) and it works pretty
> >well, except for some ports which can't be build with it. For exampl
Hello,
Recently I've started to use devel/ccache again (sometimes it takes
a while before you understand how it works) and it works pretty
well, except for some ports which can't be build with it. For example
devel/cmake.
To prevent everybody from having to re-invent the wheel, we could
introduce
24 matches
Mail list logo
