From: greg.freemyer@gmail.com (Greg Freemyer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Weird problem while compiling kernel
Date: Mon, 6 Jun 2011 16:41:17 -0400 [thread overview]
Message-ID: <BANLkTimQyHn5i6z2v-8N5dCSvQ+_Tm3qSA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=NXxzSJcUupJp6HzTLwtt9123QEA@mail.gmail.com>
On Mon, Jun 6, 2011 at 3:21 AM, Manish Katiyar <mkatiyar@gmail.com> wrote:
> /home/kernel> make net
> ?CHK ? ? include/linux/version.h
> ?CHK ? ? include/generated/utsrelease.h
> ?CALL ? ?scripts/checksyscalls.sh
> ?CC ? ? ?net/netlink/genetlink.o
> mv: cannot move `net/netlink/.genetlink.o.tmp' to
> `net/netlink/.genetlink.o.cmd': No such file or directory
> make[2]: *** [net/netlink/genetlink.o] Error 1
> make[1]: *** [net/netlink] Error 2
> make: *** [net] Error 2
> Hi,
>
> This is perhaps OOT, but I have been struggling to figure out the
> problem. While compiling kernel I'm getting the below error.
> Everything seems fine
> and I can see the file, however for some reason 'mv' can see the
> source file. strace revealed that its failing with ENOENT. I don't
> think there is anything special
> with this directory (given that other things compile just fine),
> except that this directory is on a ntfs mounted partition.
>
> /home/kernel> make net
> ?CHK ? ? include/linux/version.h
> ?CHK ? ? include/generated/utsrelease.h
> ?CALL ? ?scripts/checksyscalls.sh
> ?CC ? ? ?net/netlink/genetlink.o
> mv: cannot move `net/netlink/.genetlink.o.tmp' to
> `net/netlink/.genetlink.o.cmd': No such file or directory
> make[2]: *** [net/netlink/genetlink.o] Error 1
> make[1]: *** [net/netlink] Error 2
> make: *** [net] Error 2
>
> /home/kernel> ls -lrt net/netlink/.genetlink.o.tmp
> -rwxrwxrwx 1 root root 39301 2011-06-06 00:08 net/netlink/.genetlink.o.tmp
>
> /home/kernel> mv net/netlink/.genetlink.o.tmp net/netlink/.genetlink.o.cmd
> mv: cannot move `net/netlink/.genetlink.o.tmp' to
> `net/netlink/.genetlink.o.cmd': No such file or directory
>
> /home/kernel> mount|grep kernel
> /dev/sda1 on /home/kernel type fuseblk
> (rw,nosuid,nodev,allow_other,blksize=4096)
>
> /home/kernel> ls net/netlink/.genetlink.o.cmd
> net/netlink/.genetlink.o.cmd
>
> /home/kernel> rm net/netlink/.genetlink.o.cmd
> rm: cannot remove `net/netlink/.genetlink.o.cmd': No such file or directory
>
> /home/kernel> stat net/netlink/.genetlink.o.cmd
> ?File: `net/netlink/.genetlink.o.cmd'
> ?Size: 32093 ? ? ? ? ? Blocks: 64 ? ? ? ? IO Block: 4096 ? regular file
> Device: 801h/2049d ? ? ?Inode: 223366 ? ? ?Links: 1
> Access: (0777/-rwxrwxrwx) ?Uid: ( ? ?0/ ? ?root) ? Gid: ( ? ?0/ ? ?root)
> Access: 2011-06-06 00:08:26.394585000 -0700
> Modify: 2011-06-06 00:08:18.121035000 -0700
> Change: 2011-06-06 00:08:44.087640000 -0700
>
>
> Any suggestions, what I might be missing ?
Manish,
I know the mount command reports the filesystem r/w, but your results
make it look like the filesystem is readonly.
Did you verify you can manually write to the filesystem?
I've seen mount lie before. (It's not really a lie. It reports what
was passed on the mount command-line I believe, not the actually
functionality of the filesystem.)
Good Luck
Greg
next prev parent reply other threads:[~2011-06-06 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 7:21 Weird problem while compiling kernel Manish Katiyar
2011-06-06 20:41 ` Greg Freemyer [this message]
2011-06-06 21:21 ` Manish Katiyar
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=BANLkTimQyHn5i6z2v-8N5dCSvQ+_Tm3qSA@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).