From: "Scott Edwards" <lkml@foss.daxal.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.24.3 ARCH=um FTBFS c/o undefined reference to `i386_mmap_check'
Date: Mon, 10 Mar 2008 23:35:16 -0500 [thread overview]
Message-ID: <20080311043516.4D92F320001@mail.daxal.com> (raw)
I'm attempting to build a user mode linux kernel with some grsec features
(no PaX, apparently incompatible) I'm using 2.6.24.3 and
grsecurity-2.1.11-2.6.24.3-200803031942.patch.gz This is built on a Debian
Etch host. I have compiled linux-2.6.25-rc3-mm1 which also seems to run
without complaint.
Here's a partial log of the last lines before it fails.
LD vmlinux.o
MODPOST vmlinux.o
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD vmlinux
mm/built-in.o: In function `do_mmap_pgoff':
(.text+0xe35d): undefined reference to `i386_mmap_check'
mm/built-in.o: In function `do_brk':
(.text+0xf3be): undefined reference to `i386_mmap_check'
collect2: ld returned 1 exit status
SYSMAP System.map
nm: 'vmlinux': No such file
make: *** [vmlinux] Error 1
Script done, file is
../uml.linux-2.6.24.3-scrub-08.3b7a66a4-1774-448b-8ac3-65cb88c18950.txt
supaplex@armada: uml.linux-2.6.24.3-scrub-08$ ls -A
arch drivers kernel Module.symvers sound
block fs lib net System.map
.config .gitignore localversion-grsec .old_version .tmp_versions
.config.old grsecurity .mailmap README usr
COPYING include MAINTAINERS REPORTING-BUGS .version
CREDITS init Makefile samples .vmlinux.cmd
crypto ipc .missing-syscalls.d scripts vmlinux.o
Documentation Kbuild mm security .vmlinux.o.cmd
Thanks,
Scott
next reply other threads:[~2008-03-11 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 4:35 Scott Edwards [this message]
2008-03-11 13:40 ` Jeff Dike
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=20080311043516.4D92F320001@mail.daxal.com \
--to=lkml@foss.daxal.com \
--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®