[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFx9zHkCPUujYMaFUCbRhX5w3LeUL7UrVtMEz7W60Sz3FQ@mail.gmail.com>
Date: Sat, 29 Jun 2013 17:11:34 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Sergey Meirovich <rathamahata@...il.com>
Cc: David Airlie <airlied@...ux.ie>,
Alex Deucher <alexander.deucher@....com>,
Jerome Glisse <jglisse@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
DRI <dri-devel@...ts.freedesktop.org>
Subject: Re: Linux 3.10-rc7
On Sat, Jun 29, 2013 at 4:52 PM, Sergey Meirovich <rathamahata@...il.com> wrote:
>
> There was overheating issue, that caused forced power off in the
> middle of the first compile.
Ok, then the thing is easily explained by simply the filesystem being
shut down in an incomplete state. Sounds like the mkregtable binary
had been created but not written out, and the kernel (or rather,
shell) considers an empty executable to the same as "true", so after
the machine came back, that counts as a "successful" binary, it just
obviously doesn't write anything to stdout, which in turn then
explains the empty r200_reg_safe.h file.
So basically it boils down to: if the machine shuts down in the middle
of a build, without "make" having time to clean up partially built
files etc, you can get into strange inconsistent build trees and you
might want to do a "git clean -dqfx" to get rid of everything
generated.
But in your case it was probably just that one file. Might be a good
idea to do a clean rebuild anyway.
(Side note: I've seen 'ccache' have odd stale caches too after unclean
shutdowns, and then it's not sufficient to clean the build tree, you
need to do "ccache -C" too).
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists