From: Tarkan Erimer <tarkane@netone.com.tr>
To: linux-kernel@vger.kernel.org
Subject: [BUG] Linux-2.6.32-rc8-git2 Fails To Compile With GCC-4.4.2
Date: Tue, 01 Dec 2009 13:17:42 +0200 [thread overview]
Message-ID: <4B14FB56.4040608@netone.com.tr> (raw)
I wanted to compile linux-2.6.32-rc8-git2 with gcc-4.2.2 on opensuse
11.2. But, it failed with the following error :
PS: When I googled, I found the same error on Ubuntu Lucid forums with
gcc-4.4.2, too.
GZIP kernel/config_data.gz
CC kernel/stop_machine.o
CC [M] arch/x86/kvm/../../../virt/kvm/kvm_main.o
CC kernel/audit.o
CC kernel/auditfilter.o
CC [M] arch/x86/kvm/../../../virt/kvm/ioapic.o
CC [M] arch/x86/kvm/../../../virt/kvm/coalesced_mmio.o
CC kernel/audit_watch.o
CC [M] arch/x86/kvm/../../../virt/kvm/irq_comm.o
CC kernel/auditsc.o
CC [M] arch/x86/kvm/../../../virt/kvm/eventfd.o
CC [M] arch/x86/kvm/x86.o
CC kernel/audit_tree.o
kernel/audit_tree.c: In function ‘find_chunk’:
kernel/audit_tree.c:206: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
tarkane:/usr/src/linux-2.6.32-rc8-git2 # gcc --version
gcc (SUSE Linux) 4.4.2 [gcc-4_4-branch revision 153890]
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2009-12-01 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 11:17 Tarkan Erimer [this message]
2009-12-01 11:23 ` [BUG] Linux-2.6.32-rc8-git2 Fails To Compile With GCC-4.4.2 Bernd Petrovitsch
2009-12-01 11:39 ` Tarkan Erimer
2009-12-01 11:43 ` Bernd Petrovitsch
2009-12-01 11:48 ` Tarkan Erimer
2009-12-01 14:11 ` Michal Marek
2009-12-01 15:27 ` Tarkan Erimer
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=4B14FB56.4040608@netone.com.tr \
--to=tarkane@netone.com.tr \
--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