This is the mail archive of the
mailing list for the GCC project.
Re: Serious regressions due to newlib's HAVE_INITFINI_ARRAY (Re: [PATCH] Fix up --enable-initfini-array autodetection in configure (PR bootstrap/50237))
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Ulrich Weigand <uweigand at de dot ibm dot com>
- Cc: Paolo Bonzini <bonzini at gnu dot org>, Alexandre Oliva <aoliva at redhat dot com>, "H.J. Lu" <hjl dot tools at gmail dot com>, gcc-patches at gcc dot gnu dot org, newlib at sourceware dot org
- Date: Wed, 22 Feb 2012 16:05:06 +0100
- Subject: Re: Serious regressions due to newlib's HAVE_INITFINI_ARRAY (Re: [PATCH] Fix up --enable-initfini-array autodetection in configure (PR bootstrap/50237))
- References: <20120118232441.GO18768@tyan-ft48-01.lab.bos.redhat.com> <201202221455.q1MEtYO1014913@d06av02.portsmouth.uk.ibm.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Wed, Feb 22, 2012 at 03:55:34PM +0100, Ulrich Weigand wrote:
> However, the macro HAVE_INITFINI_ARRAY is defined anyway; this
> definition is done by an internal "newlib.h" header that is pulled
> in via the <stdio.h> include in GCC's "tsystem.h". [ This is clearly
> a violation of C namespace rules, but this has been the situation
> for all newlib releases since about 2005 ... ]
Ugh, clearly newlib bug...
> Any suggestions how to proceed with this welcome! I'd really
> like to see this fixed for 4.7, otherwise the compiler will be
> seriously broken ...
I guess the easiest would be just to rename the gcc HAVE_INITFINI_ARRAY
macro to something else, HAVE_INITFINI_ARRAY_SUPPORT or whatever.