public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Ben Gamari <bgamari.foss@gmail.com>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
	"Américo Wang" <xiyou.wangcong@gmail.com>,
	"Christoph Egger" <siccegge@cs.fau.de>,
	linux-kernel@vger.kernel.org,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	"Michal Marek" <mmarek@suse.cz>
Subject: Re: fstat suddenly return -EINVAL [Was: Bus error on make allyesconfig, kernelbuild with HEAD]
Date: Tue, 9 Nov 2010 18:29:19 +0800	[thread overview]
Message-ID: <20101109102919.GI5220@cr0.nay.redhat.com> (raw)
In-Reply-To: <8762w7efjn.fsf@gmail.com>

On Mon, Nov 08, 2010 at 03:17:16PM -0500, Ben Gamari wrote:
>On Mon, 8 Nov 2010 20:05:01 +0100, Sam Ravnborg <sam@ravnborg.org> wrote:
>> > 
>> > $ make
>> >   HOSTCC  scripts/basic/fixdep
>> > file=scripts/basic/.fixdep.d
>> > fixdep: fstat failed: Invalid argument
>> 
>> But open succedd - because we see no output from that one.
>> 
>Yes, this is true.
>
>> > How are .d files supposed to be generated?
>> 
>> They are generated by kbuild.
>> See scripts/Kbuild.include:
>> 
>> If you delete the line marked "==>" then you should have .d files are a build.
>> 
>True.
>
>> > export CC=${CROSS_COMPILE}gcc
>> > export CXX=${CROSS_COMPILE}g++
>> This part is wrong. The kernel will do this for you.
>> It should not cause any harm...
>> 
>Yeah, this is for other applications.
>
>Any idea of what could be happening?
>

No idea why this only happens to those .*.d files.
A blind guess would be commit 365b1818. :-/

      reply	other threads:[~2010-11-09 10:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 10:52 Bus error on make allyesconfig, kernelbuild with HEAD Christoph Egger
2010-07-29 11:26 ` Américo Wang
2010-07-29 11:57   ` Christoph Egger
2010-07-29 12:10   ` Christoph Egger
2010-07-30  8:43     ` Américo Wang
2010-11-06 15:07       ` Ben Gamari
2010-11-06 15:49         ` Ben Gamari
2010-11-06 16:24           ` Sam Ravnborg
2010-11-07 16:39             ` Ben Gamari
2010-11-07 16:44             ` Ben Gamari
2010-11-07 16:48               ` [PATCH] Debug fixdep Ben Gamari
2010-11-07 17:07               ` Bus error on make allyesconfig, kernelbuild with HEAD Sam Ravnborg
2010-11-07 18:09                 ` Ben Gamari
2010-11-07 22:30                   ` fstat suddenly return -EINVAL [Was: Bus error on make allyesconfig, kernelbuild with HEAD] Sam Ravnborg
2010-11-07 23:07                     ` Ben Gamari
2010-11-08 10:20                       ` Américo Wang
2010-11-08 12:38                         ` Ben Gamari
2010-11-08 18:22                           ` Sam Ravnborg
2010-11-08 18:42                             ` Ben Gamari
2010-11-08 19:05                               ` Sam Ravnborg
2010-11-08 20:17                                 ` Ben Gamari
2010-11-09 10:29                                   ` Américo Wang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101109102919.GI5220@cr0.nay.redhat.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=bgamari.foss@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.org \
    --cc=siccegge@cs.fau.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox