public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: jakub@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Linker error with latest tree on EM64T
Date: Thu, 13 Jul 2006 13:58:02 +0200	[thread overview]
Message-ID: <1152791882.4838.6.camel@localhost> (raw)
In-Reply-To: <1152788387.3024.32.camel@laptopd505.fenrus.org>

Hi Arjan,

> > when trying to build the latest tree on an EM64T Dual-Core, I am getting
> > this error:
> > 
> >   LD      .tmp_vmlinux1
> > init/built-in.o: In function `try_name':
> > do_mounts.c:(.text+0x51d): undefined reference to `__stack_chk_fail'
> > init/built-in.o: In function `name_to_dev_t':
> > (.text+0x797): undefined reference to `__stack_chk_fail'
> > init/built-in.o: In function `mount_block_root':
> > (.init.text+0x823): undefined reference to `__stack_chk_fail'
> > init/built-in.o: In function `md_run_setup':
> > (.init.text+0x1131): undefined reference to `__stack_chk_fail'
> > init/built-in.o: In function `do_header':
> > initramfs.c:(.init.text+0x24a4): undefined reference to `__stack_chk_fail'
> > arch/x86_64/kernel/built-in.o:(.text+0x2f52): more undefined references to `__st
> > ack_chk_fail' follow
> > make: *** [.tmp_vmlinux1] Error 1
> 
> you are using ubuntu which has a compiler that adds -fstack-protector
> implicitly to the compiler options, yet you don't have a kernel that
> provides this infrastructure ;)
> (I have code for that but it's not merged yet, it's pending one gcc
> patch to get merged upstream)
> in the mean time.. I'm pretty sure Sam sent a patch to Linus that adds
> -fno-stack-protector...

I couldn't find such a patch in Sam's repository, but the following
worked for me:

diff --git a/Makefile b/Makefile
index 7c010f3..b4a2a80 100644
--- a/Makefile
+++ b/Makefile
@@ -308,7 +308,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
 # Force gcc to behave correct even for buggy distributions
 CFLAGS          += $(call cc-option, -fno-stack-protector-all \
                                      -fno-stack-protector)

Thanks for the quick answer.

Regards

Marcel



  reply	other threads:[~2006-07-13 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 10:56 Linker error with latest tree on EM64T Marcel Holtmann
2006-07-13 10:59 ` Arjan van de Ven
2006-07-13 11:58   ` Marcel Holtmann [this message]
2006-07-13 13:26     ` Sam Ravnborg
2006-07-13 13:30       ` Marcel Holtmann
2006-07-13 16:10         ` Sam Ravnborg
2006-07-13 16:17           ` Marcel Holtmann
2006-07-13 18:29             ` Sam Ravnborg

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=1152791882.4838.6.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=arjan@infradead.org \
    --cc=jakub@redhat.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