All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Vishnupradeep <intermedia.vishnu@gmail.com>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] linux-3.0.4 compile error on file arch/x86/include/asm/unistd_64.h
Date: Tue, 30 Aug 2011 20:26:37 +0200	[thread overview]
Message-ID: <4E5D2B5D.2070800@gmail.com> (raw)
In-Reply-To: <20110830181639.GB24865@kroah.com>

On 08/30/2011 08:16 PM, Greg KH wrote:
> On Tue, Aug 30, 2011 at 11:37:33PM +0530, Vishnupradeep wrote:
>> Yes, i am sure. I just downloaded from kernel.org and ran "make"
>
> That's not how to properly configure and build a kernel.  Have you read
> the documentation on how to do this?  Can you attach your .config file
> that you used and ran into this error?

Well, there is nothing like "#Define" on that line:
$ wget ftp://ftp.kernel.org/pub/linux/kernel/v3.0/linux-3.0.4.tar.bz2
...
2011-08-30 20:18:53 (8.88 MB/s) - `linux-3.0.4.tar.bz2' saved [76759291]

$ tar xf linux-3.0.4.tar.bz2
$ sed -n '668 p' linux-3.0.4/arch/x86/include/asm/unistd_64.h
#define __NR_fanotify_mark                      301




So my guess is that he has a failing memory. (Single bit flip in d->D.)

regards,
-- 
js

  reply	other threads:[~2011-08-30 18:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30  6:07 linux-3.0.4 compile error on file arch/x86/include/asm/unistd_64.h Vishnupradeep
2011-08-30  7:17 ` Jiri Slaby
2011-08-30 18:07   ` Vishnupradeep
2011-08-30 18:16     ` [stable] " Greg KH
2011-08-30 18:26       ` Jiri Slaby [this message]
2011-08-30 18:48       ` Vishnupradeep
2011-08-30 19:06         ` Greg KH
2011-08-31  2:07           ` Vishnupradeep
2011-08-31  4:47             ` Vishnupradeep
2011-08-31 15:38               ` Greg KH
2011-08-31 11:46             ` [OT] " el es

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=4E5D2B5D.2070800@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=greg@kroah.com \
    --cc=intermedia.vishnu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.