Hi,
until recently, 'make bin' was a very smart tool: it recompiled only
necessary .cc files, not everything. That was lifesaving: instead of
having to wait for 5 minutes, i got the results of my changes in 5
seconds. Unfortunately, this is no longer the case: no matter how
trivial the change,
Janek Warchoł janek.lilyp...@gmail.com writes:
until recently, 'make bin' was a very smart tool: it recompiled only
necessary .cc files, not everything. That was lifesaving: instead of
having to wait for 5 minutes, i got the results of my changes in 5
seconds. Unfortunately, this is no
Le 03/07/2012 19:23, Janek Warchoł disait :
Hi,
until recently, 'make bin' was a very smart tool: it recompiled only
necessary .cc files, not everything. That was lifesaving: instead of
having to wait for 5 minutes, i got the results of my changes in 5
seconds. Unfortunately, this is no
On 3 juil. 2012, at 19:46, Jean-Charles Malahieude wrote:
Le 03/07/2012 19:23, Janek Warchoł disait :
Hi,
until recently, 'make bin' was a very smart tool: it recompiled only
necessary .cc files, not everything. That was lifesaving: instead of
having to wait for 5 minutes, i got the
On Tue, Jul 3, 2012 at 7:35 PM, David Kastrup d...@gnu.org wrote:
So obviously something else is wrong here. Try removing
lily/out/smobs.dep and lily/out/smobs.o and see whether this helps.
To be expected is a large amount of recompilation _once_ since a lot of
files need smobs.hh. If it
On Tue, Jul 3, 2012 at 8:55 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
Now comes the most surprising part: just to make sure, i just did the
following:
checkout origin/master # local master contained a revert of that commit
make from scratch
add a trivial change
make bin
Janek Warchoł janek.lilyp...@gmail.com writes:
On Tue, Jul 3, 2012 at 8:55 PM, Janek Warchoł janek.lilyp...@gmail.com
wrote:
Now comes the most surprising part: just to make sure, i just did
the following:
checkout origin/master # local master contained a revert of that commit
make from
It is almost certainly a problem with your system clock. If you have
touched source files with a future clock, and now the clock is right,
then compiled files will be outdated (older than the source file)
immediately after compilation again.
There is a special built-in target in GNU make:
Werner LEMBERG w...@gnu.org writes:
It is almost certainly a problem with your system clock. If you have
touched source files with a future clock, and now the clock is right,
then compiled files will be outdated (older than the source file)
immediately after compilation again.
There is a
On Tue, Jul 3, 2012 at 10:19 PM, David Kastrup d...@gnu.org wrote:
It is almost certainly a problem with your system clock. If you have
touched source files with a future clock, and now the clock is right,
then compiled files will be outdated (older than the source file)
immediately after
10 matches
Mail list logo
