public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lasse-gccbug-2009 at mail dot plastictree dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/39641] Compiling Linux 2.6.28.6 ends with a segfault on net/core/skbuff.c Date: Sun, 05 Apr 2009 15:19:00 -0000 [thread overview] Message-ID: <20090405151945.9442.qmail@sourceware.org> (raw) In-Reply-To: <bug-39641-17529@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from lasse-gccbug-2009 at mail dot plastictree dot net 2009-04-05 15:19 ------- Segfault does not occur when omitting '-ffreestanding'. Segfault does not occur when using '-save-temps'. When I add '-save-temps' to 'arch/x86/Makefile' in the same location in which '-ffreestanding' occurs, 'make' runs through. I have not tested whether the resulting kernel works. Moreover, in that Makefile, it reads: # temporary until string.h is fixed KBUILD_CFLAGS += -ffreestanding So, it appears that '-ffreestanding' is itself a workaround for something. Another approach: obtain 'skbuff.i' via '-save-temps' and then copy it to 'net/core/skbuff.c'. Then 'make' will also run through. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39641
next prev parent reply other threads:[~2009-04-05 15:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-04 22:23 [Bug c/39641] New: Compiling Linux 2.6.28.6 ends with a segfault lasse-gccbug-2009 at mail dot plastictree dot net 2009-04-04 22:27 ` [Bug c/39641] " lasse-gccbug-2009 at mail dot plastictree dot net 2009-04-04 22:29 ` lasse-gccbug-2009 at mail dot plastictree dot net 2009-04-05 15:19 ` lasse-gccbug-2009 at mail dot plastictree dot net [this message] 2009-04-22 23:39 ` [Bug middle-end/39641] Compiling Linux 2.6.28.6 ends with a segfault on net/core/skbuff.c pinskia at gcc dot gnu dot org 2009-04-23 6:43 ` lasse-gccbug-2009 at mail dot plastictree dot net
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=20090405151945.9442.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).