From: debian developer <debiandev@gmail.com>
To: linux kernel <kernelnewbies@nl.linux.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Unable to compile 2.6.30-rc7 on RHEL 4 - GCC 3.4.6
Date: Mon, 25 May 2009 22:26:25 +0530 [thread overview]
Message-ID: <f24d23310905250956u231fcd90u54d75894b9b91b9a@mail.gmail.com> (raw)
Hi all,
I am getting this error when trying to compile the latest rc:
/in/inndesk171/linux-2.6.28/arch/x86/Makefile:82: stack protector
enabled but no compiler support
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CALL scripts/checksyscalls.sh
CC init/main.o
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h: In
function `start_kernel':
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1590:
warning: asm operand 1 probably doesn't match constraints
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1570:
warning: asm operand 2 probably doesn't match constraints
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1590:
warning: asm operand 1 probably doesn't match constraints
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1570:
warning: asm operand 2 probably doesn't match constraints
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1599:
warning: asm operand 1 probably doesn't match constraints
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1590:
error: impossible constraint in `asm'
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1570:
error: impossible constraint in `asm'
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1590:
error: impossible constraint in `asm'
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1570:
error: impossible constraint in `asm'
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1599:
error: impossible constraint in `asm'
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1568:
warning: 'f' might be used uninitialized in this function
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1568:
warning: 'f' might be used uninitialized in this function
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1568:
warning: 'f' might be used uninitialized in this function
/in/inndesk171/linux-2.6.28/arch/x86/include/asm/paravirt.h:1568:
warning: 'f' might be used uninitialized in this function
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2
The gcc version is as follows:
debiandev@inndesk171[80] gcc -v
Reading specs from /usr/lib/gcc/x86_64-redhat-linux/3.4.6/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-java-awt=gtk
--host=x86_64-redhat-linux
Thread model: posix
gcc version 3.4.6 20060404 (Red Hat 3.4.6-9)
Is this gcc version no longer usable to compile the latest kernel?
Thanks,
DD
next reply other threads:[~2009-05-25 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 16:56 debian developer [this message]
2009-05-25 21:17 ` Simon König
2009-05-26 16:59 ` Stefan Richter
2009-05-25 21:45 ` GeunSik Lim
2009-05-26 5:56 ` debian developer
2009-05-26 7:26 ` GeunSik Lim
2009-05-26 7:41 ` Mikael Pettersson
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=f24d23310905250956u231fcd90u54d75894b9b91b9a@mail.gmail.com \
--to=debiandev@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--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®