mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Hazelton <dshadowwolf@gmail.com>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	fengguang.wu@intel.com, kosaki.motohiro@jp.fujitsu.com,
	drepper@gmail.com, paulmck@linux.vnet.ibm.com
Subject: tools/vm build fails
Date: Mon, 22 Oct 2012 20:00:56 -0400	[thread overview]
Message-ID: <5085DE38.6030906@gmail.com> (raw)

After doing any build in the kernel (last attempt was an allmodconfig) 
I've tried to build the 'vm' tool in tools/vm and the build fails - 
looks to be fallout from the uapi header work.

[madman@localhost tools]$ make V=1 vm
make -C vm/
make[1]: Entering directory `/home/madman/sources/linux-2.6/tools/vm'
gcc -Wall -Wextra -o page-types page-types.c
In file included from page-types.c:38:0:
../../include/linux/kernel-page-flags.h:4:42: fatal error: 
uapi/linux/kernel-page-flags.h: No such file or directory
compilation terminated.
make[1]: *** [page-types] Error 1
make[1]: Leaving directory `/home/madman/sources/linux-2.6/tools/vm'
make: *** [vm] Error 2

I'm not a kernel developer (I've tried and been unable to wrap my head 
around any part that I was going to try working on :( )and was just 
trying bits in tools/ at random to see what, exactly, they were and this 
kept happening, no matter the state of the tree.

I updated my git tree about 3 hours ago to mirror the latest Linus from 
git.kernel.org after having run into this error yesterday and deciding I 
must have done something wrong. This looks like it might be a missing -I 
or similar since the file does exist and is at that exact path from the 
file that is directly including it.

DRH

             reply	other threads:[~2012-10-23  0:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  0:00 Daniel Hazelton [this message]
2012-10-23  0:20 ` Fengguang Wu

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=5085DE38.6030906@gmail.com \
    --to=dshadowwolf@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=drepper@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    /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

Powered by JetHome