linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Boris Bezlaj <boris@gajba.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: 2.5.66 compile fails under ppc32
Date: Fri, 28 Mar 2003 12:19:30 +0100	[thread overview]
Message-ID: <20030328111930.GA2451@gajba.net> (raw)


Hello,

did anyone encounter this problem when compiling 2.5.66 under ppc32 ?

| include/linux/swapops.h: In function `pte_to_swp_entry':
| include/linux/swapops.h:54: warning: implicit declaration of function `pte_file'
| mm/fremap.c: In function `sys_remap_file_pages':
| mm/fremap.c:139: `PTE_FILE_MAX_BITS' undeclared (first use in this function)

PTE_FILE_MAX_BITS is not defined anywhere.. for ppc64 it's in:

include/asm-ppc64/pgtable.h:#define PTE_FILE_MAX_BITS   (BITS_PER_LONG - PTE_SHIFT)

but not for ppc arch.

Anyone else or is it just me?
--

  Boris

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-03-28 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 11:19 Boris Bezlaj [this message]
2003-03-28 12:06 ` 2.5.66 compile fails under ppc32 Paul Mackerras

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=20030328111930.GA2451@gajba.net \
    --to=boris@gajba.net \
    --cc=linuxppc-dev@lists.linuxppc.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).