On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich rathamahata@gmail.com wrote:
(and possibly the mkregtable binary) and trying again might fix it.
Removing mkregtable has indeed the compile issue for me. Thanks!
Ok, so something failed at an earlier build. That error is probably long gone, though, since the subsequent build failure ends up being just a symptom rather than the underlying cause.
Which still leaves us with the question of how this happened, and a potentially fragile Makefile.
Radeon/drm people - any ideas how that mkregtable failure happened?
Linus
On Sat, Jun 29, 2013 at 4:52 PM, Sergey Meirovich rathamahata@gmail.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
On Sun, Jun 30, 2013 at 8:13 AM, Linus Torvalds torvalds@linux-foundation.org wrote:
On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich rathamahata@gmail.com wrote:
(and possibly the mkregtable binary) and trying again might fix it.
Removing mkregtable has indeed the compile issue for me. Thanks!
Ok, so something failed at an earlier build. That error is probably long gone, though, since the subsequent build failure ends up being just a symptom rather than the underlying cause.
Which still leaves us with the question of how this happened, and a potentially fragile Makefile.
Radeon/drm people - any ideas how that mkregtable failure happened?
I'd care if we can definitely rule out previous power fails or forced reboots. Otherwise just seems like noise, if gcc can produce 0 sized binaries then I'm sure we'd have other issues.
Dave.
On 30 June 2013 01:13, Linus Torvalds torvalds@linux-foundation.org wrote:
On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich rathamahata@gmail.com wrote:
(and possibly the mkregtable binary) and trying again might fix it.
Removing mkregtable has indeed the compile issue for me. Thanks!
Ok, so something failed at an earlier build. That error is probably long gone, though, since the subsequent build failure ends up being just a symptom rather than the underlying cause.
There was overheating issue, that caused forced power off in the middle of the first compile.
Which still leaves us with the question of how this happened, and a potentially fragile Makefile.
Radeon/drm people - any ideas how that mkregtable failure happened?
Linus
dri-devel@lists.freedesktop.org
-
Dave Airlie -
Linus Torvalds -
Sergey Meirovich