public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.27 -- memory.c:50:22: asm/rmap.h: No such file or directory
Date: 20 Jul 2002 21:32:13 -0400	[thread overview]
Message-ID: <1027215133.1863.37.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L.0207202153190.12241-100000@imladris.surriel.com>

On Sat, 2002-07-20 at 20:53, Rik van Riel wrote:
> On 20 Jul 2002, Miles Lane wrote:
> > On Sat, 2002-07-20 at 20:47, Rik van Riel wrote:
> > > On 20 Jul 2002, Miles Lane wrote:
> > >
> > > > Hmm.  This problem looks pretty straightforward.
> > >
> > > Indeed.  Have you tried 'make oldconfig' to set the
> > > symlink in include/ ?
> >
> > Yeah.  I mention that in my first message.  ;-)
> 
> So, does the symlink exist ?
> 
> I'm asking that because gcc has no problem finding <asm/rmap.h>
> here or at anybody else's place ;)

Hmm.  I don't have an asm directory, in spite of running oldconfig.
I suspect this problem is a result of the previous problem
I reported with "make mrproper" having an error?

I will try creating a completely new tree and then use that 
.config file (make oldconfig dep all install modules modules_install).

Thanks,
	Miles


       reply	other threads:[~2002-07-21  1:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L.0207202153190.12241-100000@imladris.surriel.com>
2002-07-21  1:32 ` Miles Lane [this message]
2002-07-21  0:27 2.5.27 -- memory.c:50:22: asm/rmap.h: No such file or directory Miles Lane
2002-07-21  0:34 ` Miles Lane
2002-07-21  0:47   ` Rik van Riel
2002-07-21  1:37   ` Miles Lane
2002-07-21  5:39     ` Tomas Szepe
2002-07-22 14:31       ` Kai Germaschewski

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=1027215133.1863.37.camel@localhost.localdomain \
    --to=miles@megapathdsl.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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