[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Use gcc 4.0 to build glibc on all architectures

On Thu, Feb 16, 2006 at 12:00:36AM +0100, Aurelien Jarno wrote:
> A few Debian architectures, are still using and old gcc to build the 
> glibc. I think we should try to move slowly to gcc 4.0, as other
> versions (mainly gcc-3.4), won't be supported as gcc 4.0 will be. Also
> I have hurd they've been some discussions about shipping etch without
> gcc-3.4.
> - hurd-i386 is using gcc 3.3. I will contact the hurd porters the same
>   way as for m68k.

glibc-2.3.6 supports gcc-4.0 on GNU/Hurd upstream.  There have been some
binutils issues involving z_relro nobody was able to track down yet,

The attached patch makes glibc build fine on hurd-i386.



Michael Banck
Debian Developer
Index: sysdeps/hurd.mk
--- sysdeps/hurd.mk	(revision 1182)
+++ sysdeps/hurd.mk	(working copy)
@@ -6,10 +6,6 @@
 libc = libc0.3
 slibdir = /lib
-# work around to build, gcc-3.4/gcc-4.0 are not tested yet.
-CC = gcc-3.3
-BUILD_CC = gcc-3.3
 # Glibc should really do this for us.
 define libc_extra_install
 mkdir -p debian/tmp-$(curpass)/lib
@@ -21,6 +17,7 @@
-# TLS is broken currently and results in Mach panicing
-libc_extra_config_options := $(extra_config_options) --without-tls
+# TLS is broken currently and results in Mach panicing.
+# ld.so is broken currently if z_relro is used.
+libc_extra_config_options := $(extra_config_options) --without-tls libc_cv_z_relro=no

Reply to: