This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nscd/5210] New: fstack projector is not supported on alpha and does strange things...
- From: "oliver at linux-kernel dot at" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 23 Oct 2007 08:37:07 -0000
- Subject: [Bug nscd/5210] New: fstack projector is not supported on alpha and does strange things...
- Reply-to: sourceware-bugzilla at sourceware dot org
We have experienced quite often problems with the unsupported fstack-protector
gcc option on alpha. However, glibc does now check for it in configure(.in) and
adds that to the gcc options - that's bad for alpha. gcc only spots a warning
when this option is used on alpha, but it seems there's "something else" also
going on in gcc internals and therefor sometimes builds break with fstack
protector - we haven't yet done much investigation on this problem, as disabling
the option was much easier :-)
A small patch to configure.in should fix the problem (I see it introduced with
glibc 2.7) on alpha:
[oliver@gosa glibc-20071017T2029]$ diff -uNr configure.in /tmp/configure.in
--- configure.in 2007-06-08 05:16:36.000000000 +0200
+++ /tmp/configure.in 2007-10-23 10:30:23.000000000 +0200
@@ -1638,6 +1638,9 @@
else
libc_cv_ssp=no
fi
+if test $base_machine = alpha; then
+ libc_cv_ssp=no
+fi
rm -f conftest*])
AC_SUBST(libc_cv_ssp)
(I've choosen nscd as component, as there is an explicit check in the Makefile
for it...)
--
Summary: fstack projector is not supported on alpha and does
strange things...
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nscd
AssignedTo: drepper at redhat dot com
ReportedBy: oliver at linux-kernel dot at
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: alpha-redhat-linux
GCC host triplet: alpha-redhat-linux
GCC target triplet: alpha-redhat-linux
http://sourceware.org/bugzilla/show_bug.cgi?id=5210
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.