mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Takeo Tung" <kernel@takeo.idv.tw>
To: "Michal Marek" <mmarek@suse.cz>
Cc: <linux-kernel@vger.kernel.org>, "Christoph Hellwig" <hch@lst.de>,
	<kernel@takeo.idv.tw>
Subject: Re: linux-next-20100608 will /bin/sh: scripts/basic/fixdep: Permission denied
Date: Sat, 12 Jun 2010 16:44:48 +0800	[thread overview]
Message-ID: <F8C0125B8F424A279E9679EAC24AC983@TAKEOW7NB1> (raw)
In-Reply-To: <4C129778.7040409@suse.cz>

Hello,

yes.

1. I complier liux-next-20100608 kernel, and boot the linux-next-20100608 
kernel, and try re-complier kernel, will found this message.
    /bin/sh: scripts/basic/fixdep: Permission denied

2. reboot other safe kernel, and revert the above patch, and complier it, 
and boot the new kernel, seems no this error.
    but I don't know why, bcoz seems code is ok.

Thanks,
Takeo Tung

--------------------------------------------------
From: "Michal Marek" <mmarek@suse.cz>
Sent: Saturday, June 12, 2010 4:07 AM
To: "Takeo Tung" <kernel@takeo.idv.tw>
Cc: <linux-kernel@vger.kernel.org>; "Christoph Hellwig" <hch@lst.de>
Subject: Re: linux-next-20100608 will /bin/sh: scripts/basic/fixdep: 
Permission denied

> On 11.6.2010 17:13, Takeo Tung wrote:
>> Dear All,
>>
>> I using linux-next-20100608 kernel, but if re-complier the kernel will
>> found
>> this messages.
>>
>> root@kernel-x86:/usr/src/linux# make oldconfig
>>  HOSTCC  scripts/basic/fixdep
>> /bin/sh: scripts/basic/fixdep: Permission denied
>> make[1]: *** [scripts/basic/fixdep] Error 1
>> make: *** [scripts_basic] Error 2
>>
>> But if I revert this patch, seems all back to normal, pls help me this is
>> bug patch or need adjust some system config?
>>
>> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=9d9b938248736826e86db9b16a3b435bdb5d649f
>
> Do I understand it correctly that you can't rebuild your kernel if
> you're running linux-next-20100608 and that the problem goes away if you
> revert the above patch, recompile somewhere else and boot the new
> kernel? I.e. it's unlikely a problem with fixdep itself?
>
> Adding Christoph Hellwig to cc.
>
> Michal
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
> 

  reply	other threads:[~2010-06-12  8:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 15:13 Takeo Tung
2010-06-11 20:07 ` Michal Marek
2010-06-12  8:44   ` Takeo Tung [this message]
2010-06-12  9:49     ` Christoph Hellwig
2010-06-12 19:35       ` Takeo Tung
2010-06-28 10:52       ` block: unify flags for struct bio and struct request will kernel panic Takeo Tung
2010-07-07 23:05         ` [PATCH] struct io panic on raid1 - " Takeo Tung
2010-07-07 23:17           ` Christoph Hellwig
2010-07-07 23:48             ` Neil Brown
2010-07-08  0:43               ` Takeo Tung
2010-07-08  1:15                 ` Neil Brown
2010-07-08  1:42                   ` Takeo Tung
  -- strict thread matches above, loose matches on Subject: below --
2010-06-11 15:04 linux-next-20100608 will /bin/sh: scripts/basic/fixdep: Permission denied Takeo Tung

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=F8C0125B8F424A279E9679EAC24AC983@TAKEOW7NB1 \
    --to=kernel@takeo.idv.tw \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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

all inboxes | Powered by JetHome®