[PATCH] glibc 2.7 compilation failure with GCC 4.2.x due to 486+-specific memmove() redeclaration and _FORTIFY_SOURCEry

[Nix]

On 29 Oct 2007, Mike Frysinger verbalised:
> ive gotten a report or two in Gentoo about it, but i havent been able to 
> reproduce it myself

I don't see how to make it go away, personally. It should turn up on any
platform that uses sysdeps/i386/i486/bits/string.h, as far as I can see.

I configured this particular platform on a PIII with this shell script:

#!/bin/sh

unset CONFIG_SITE
export CFLAGS="-O2 -march=native -pipe"
export ASFLAGS="$CFLAGS"
export LDFLAGS="-specs=specs.no-as-needed"

CONFIGURE=$1
shift
$CONFIGURE --build=i686-pc-linux-gnu "$@"


(specs.no-as-needed is the default specs file generated by GCC 4.2.x:
otherwise, the default (customized) specs file on my site turns on
--build-id and --as-needed by default at link time, and the latter at
least is bad for the glibc testsuite. I have patches to allow glibc to
build with a default-on --build-id, if you want them, but they're so
trivial I thought nobody would care...)


This bug isn't a local patching thing: I see it with a pristine 2.7
tree.