[arch-dev-public] [signoff] glibc-2.12-3
The new defaults in makepkg more aggressively strip shared libraries. Doing this for certain libraries in glibc causes gdb breakage so all file stripping must be done manually. Also, grab the latest from the glibc-2.12 branch as it contains a couple of new bugfixes. Signoff both, Allan
On Sun, Jun 20, 2010 at 1:28 AM, Allan McRae <allan@archlinux.org> wrote:
The new defaults in makepkg more aggressively strip shared libraries. Doing this for certain libraries in glibc causes gdb breakage so all file stripping must be done manually.
Also, grab the latest from the glibc-2.12 branch as it contains a couple of new bugfixes.
Nothing has broken on me today on either architecture. Signoff both. -Dan
On 06/21/2010 05:14 AM, Dan McGee wrote:
On Sun, Jun 20, 2010 at 1:28 AM, Allan McRae<allan@archlinux.org> wrote:
The new defaults in makepkg more aggressively strip shared libraries. Doing this for certain libraries in glibc causes gdb breakage so all file stripping must be done manually.
Also, grab the latest from the glibc-2.12 branch as it contains a couple of new bugfixes.
Nothing has broken on me today on either architecture. Signoff both.
-Dan
same here. signoff x86_64 -- Ionuț
Am 20.06.2010 08:28, schrieb Allan McRae:
The new defaults in makepkg more aggressively strip shared libraries. Doing this for certain libraries in glibc causes gdb breakage so all file stripping must be done manually.
Also, grab the latest from the glibc-2.12 branch as it contains a couple of new bugfixes.
Signoff both, Allan
Signoff both.
On Sun, 2010-06-20 at 16:28 +1000, Allan McRae wrote:
The new defaults in makepkg more aggressively strip shared libraries. Doing this for certain libraries in glibc causes gdb breakage so all file stripping must be done manually.
Also, grab the latest from the glibc-2.12 branch as it contains a couple of new bugfixes.
Signoff both, Allan
Signoff both, my testing chroots still work fine with this.
On Sun, 2010-06-20 at 16:28 +1000, Allan McRae wrote:
The new defaults in makepkg more aggressively strip shared libraries. Doing this for certain libraries in glibc causes gdb breakage so all file stripping must be done manually.
Also, grab the latest from the glibc-2.12 branch as it contains a couple of new bugfixes.
Signoff both, Allan
Fun, though gdb should work with the new version, valgrind does not: valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2
On 23/06/10 19:21, Jan de Groot wrote:
On Sun, 2010-06-20 at 16:28 +1000, Allan McRae wrote:
The new defaults in makepkg more aggressively strip shared libraries. Doing this for certain libraries in glibc causes gdb breakage so all file stripping must be done manually.
Also, grab the latest from the glibc-2.12 branch as it contains a couple of new bugfixes.
Signoff both, Allan
Fun, though gdb should work with the new version, valgrind does not:
valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2
I am getting good at breaking valgrind on x86_64! When are people going to learn that i686 is the future... :P Starting some rebuilds now to figure this out. I guess it is something with PIC/PIE on x86_64 meaning I can not strip ld-linux.so.2 so much. Allan
participants (5)
-
Allan McRae
-
Dan McGee
-
Ionuț Bîru
-
Jan de Groot
-
Thomas Bächler