A compilation of an ARM toolchain with glibc 2.7 using crosstool-ng
failed with a gcc error in glibc-2.7/posix/regex_internal.c, more
concretly in the function build_wcs_upper_buffer(). The return type of
the function prototype in regex_internal.h doesn't correspond with the
return type of this function in regex_internal.c.
The attached patch corrects the return type of the function prototype
in regex_internal.h
/trunk/patches/glibc/2.7/180-glibc-2.7-build_wcs_upper_buffer.patch | 22 22 0 0 +++++++++++
1 file changed, 22 insertions(+)
Based on feedback from Mike Frysinger, add the following patchset for
glibc-2.7. Not stress-tested, but at least make it available for
interested testers.
According to Mike Frysinger, this patch was removed from Gentoo in the
2.3.x series and didn't seem to cause any adverse effects. So toss it
from the patch directories for glibc 2.5 and up.
According to Mike Frysinger, this patch hasn't been necessary since
glibc-2.4+, so turf it from glibc patches 2.5 and up. If someone
complains, it can always go back in.
- use ports addon even when installing headers,
- use optimisation (-O) when installing headers, to avoid unnecessary warnings (thanks Robert P. J. DAY for pointing this out!),
- lowest kernel version to use is only X.Y.Z, not X.Y.Z.T,
- a bit of preparations for NPTL (RSN I hope),
- fix fixing the linker scripts (changing the backup file is kind of useless and stupid);
Shut uClibc finish step: there really is nothing to do;
Add a patch for glibc-2.3.6 weak aliases handling on some archs (ARM and ALPHA at least);
Did not catch the make errors: fixed the pattern matching in scripts/functions;
Introduce a new log level, ALL:
- send components' build messages there,
- DEBUG log level is destined only for crosstool-NG debug messages,
- migrate sub-actions to use appropriate log levels;
Update the armeb-unknown-linux-gnu sample:
- it builds!
- uses gcc-4.0.4 and glibc-2.3.6,
- updated to latest config options set.
You might just say: 'Yeah! crosstool-NG's got its own repo!".
Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup.
That means I'm putting backups in place in the afternoon.
That also means we've lost history... :-(
