From: Tej <bewith.tej@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: sam@ravnborg.org
Subject: [PATCH] build error: 2.6.17-rc5
Date: Thu, 23 Oct 2008 01:31:02 +0530 [thread overview]
Message-ID: <f1c9d250810221301hb514aady73203bf489e0932b@mail.gmail.com> (raw)
observed following build error for 2.6.17-rc5 kernel (git repo)
<---snip---->
/opt/Testing/Tools/linux-2.6/init/do_mounts.c:115: undefined reference
to `__stack_chk_fail'
init/built-in.o: In function `name_to_dev_t':
/opt/Testing/Tools/linux-2.6/init/do_mounts.c:206: undefined reference
to `__stack_chk_fail'
init/built-in.o: In function `change_floppy':
/opt/Testing/Tools/linux-2.6/init/do_mounts.c:363: undefined reference
to `__stack_chk_fail'
init/built-in.o: In function `mount_block_root':
/opt/Testing/Tools/linux-2.6/init/do_mounts.c:321: undefined reference
to `__stack_chk_fail'
init/built-in.o: In function `do_header':
/opt/Testing/Tools/linux-2.6/init/initramfs.c:206: undefined reference
to `__stack_chk_fail'
arch/i386/kernel/built-in.o:/opt/Testing/Tools/linux-2.6/arch/i386/kernel/ptrace.c:634:
more undefined references to `__stack_chk_fail' follow
make: *** [.tmp_vmlinux1] Error 1
attached patch solve problem, which seems to be obvious by looking at
defination of "__stack_chk_fail" with subsequent kernel versions.
Signed-off-by: Tej Parkash <bewith.tej@gmail.com>
diff --git a/Makefile b/Makefile
index 435d209..d2afeea 100644
--- a/Makefile
+++ b/Makefile
@@ -306,7 +306,7 @@ LINUXINCLUDE := -Iinclude \
CPPFLAGS := -D__KERNEL__ $(LINUXINCLUDE)
CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
- -fno-strict-aliasing -fno-common
+ -fno-strict-aliasing -fno-common -fno-stack-protector
AFLAGS := -D__ASSEMBLY__
# Read KERNELRELEASE from .kernelrelease (if it exists)
reply other threads:[~2008-10-22 20:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f1c9d250810221301hb514aady73203bf489e0932b@mail.gmail.com \
--to=bewith.tej@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®