From: "Oliver Pitzeier" <o.pitzeier@uptime.at>
To: "'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: Problems with mm on Alpha...
Date: Wed, 8 May 2002 11:46:28 +0200 [thread overview]
Message-ID: <003701c1f675$3d1c5cc0$010b10ac@sbp.uptime.at> (raw)
In-Reply-To: <20020508113428.D31998@dualathlon.random>
Hi volks!
Can anybody help/explain this to me:
[ ... ]
make[1]: Entering directory `/root/linux-2.5.14/mm'
make all_targets
make[2]: Entering directory `/root/linux-2.5.14/mm'
gcc -D__KERNEL__ -I/root/linux-2.5.14/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6
-DKBUILD_BASENAME=memory -c -o memory.o memory.c
memory.c: In function `__free_pte':
memory.c:80: warning: implicit declaration of function `pte_pfn'
memory.c:81: warning: implicit declaration of function `pfn_valid'
memory.c:83: warning: implicit declaration of function `pfn_to_page'
memory.c:83: warning: assignment makes pointer from integer without a
cast
memory.c: In function `copy_page_range':
memory.c:289: warning: assignment makes pointer from integer without a
cast
memory.c: In function `zap_pte_range':
memory.c:369: warning: assignment makes pointer from integer without a
cast
memory.c: In function `follow_page':
memory.c:490: warning: return makes pointer from integer without a cast
memory.c: In function `remap_pte_range':
memory.c:879: invalid type argument of `->'
memory.c:880: warning: implicit declaration of function `pfn_pte'
memory.c:880: incompatible types in assignment
memory.c: In function `do_wp_page':
memory.c:996: warning: assignment makes pointer from integer without a
cast
make[2]: *** [memory.o] Error 1
make[2]: Leaving directory `/root/linux-2.5.14/mm'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/root/linux-2.5.14/mm'
make: *** [_dir_mm] Error 2
[ ... ]
-Oliver
next prev parent reply other threads:[~2002-05-08 9:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 14:54 2.4.19pre8aa2 Andrea Arcangeli
2002-05-04 15:02 ` 2.4.19pre8aa2 Christoph Hellwig
2002-05-04 23:34 ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05 3:04 ` 2.4.19pre8aa2 Keith Owens
2002-05-05 7:40 ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05 8:04 ` 2.4.19pre8aa2 Keith Owens
2002-05-05 8:16 ` 2.4.19pre8aa2 Keith Owens
2002-05-05 13:38 ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05 0:25 ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-04 18:56 ` 2.4.19pre8aa2 Francois Romieu
2002-05-05 0:14 ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-08 2:27 ` 2.4.19pre8aa2 Pozsar Balazs
2002-05-08 9:34 ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-08 9:46 ` Oliver Pitzeier [this message]
2002-05-08 10:54 ` Problems with mm on Alpha Ivan Kokshaysky
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='003701c1f675$3d1c5cc0$010b10ac@sbp.uptime.at' \
--to=o.pitzeier@uptime.at \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®