From: Jiri Slaby <jirislaby@gmail.com>
To: Vishnupradeep <intermedia.vishnu@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: linux-3.0.4 compile error on file arch/x86/include/asm/unistd_64.h
Date: Tue, 30 Aug 2011 09:17:55 +0200 [thread overview]
Message-ID: <4E5C8EA3.7060304@gmail.com> (raw)
In-Reply-To: <CACk0-C9jZatg+v=7DPJtkp3G1k_eiZbwSPDAgqabMyedmKd9YA@mail.gmail.com>
On 08/30/2011 08:07 AM, Vishnupradeep wrote:
> CC net/ipv4/ip_forward.o
> CC net/ipv4/ip_options.o
> CC net/ipv4/ip_output.o
> CC net/ipv4/ip_sockglue.o
> In file included from
> /media/Portable/linux-kernel/linux-3.0.4/arch/x86/include/asm/unistd.h:5:0,
> from include/linux/unistd.h:7,
> from
> /media/Portable/linux-kernel/linux-3.0.4/arch/x86/include/asm/seccomp_64.h:4,
> from
> /media/Portable/linux-kernel/linux-3.0.4/arch/x86/include/asm/seccomp.h:4,
> from include/linux/seccomp.h:8,
> from include/linux/sched.h:80,
> from
> /media/Portable/linux-kernel/linux-3.0.4/arch/x86/include/asm/compat.h:8,
> from include/linux/compat.h:18,
> from include/linux/ethtool.h:17,
> from include/linux/netdevice.h:48,
> from include/linux/inetdevice.h:8,
> from net/ipv4/ip_sockglue.c:24:
> /media/Portable/linux-kernel/linux-3.0.4/arch/x86/include/asm/unistd_64.h:668:2:
> error: invalid preprocessing directive #Define
There is nothing like "#Define" here. Are you sure you didn't modify the
file?
--
js
next prev parent reply other threads:[~2011-08-30 7:17 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 [this message]
2011-08-30 18:07 ` Vishnupradeep
2011-08-30 18:16 ` [stable] " Greg KH
2011-08-30 18:26 ` Jiri Slaby
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=4E5C8EA3.7060304@gmail.com \
--to=jirislaby@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox