[opensuse-factory] glibc 2.14 coming to Factory
I've submitted yesterday glibc 2.14 to Base:System and was surprised that all packages build fine there. The most significant change in glibc 2.14 was the disabling of the sunrpc code - and I had reverted this change since libtirpc is not a full replacement for sunrpc yet. libtirpc works for many applications but I could not get others working. The NEWS file for 2.14 reads. Our glibc has additional bug fixes * The following bugs are resolved with this release: 386, 6420, 7101, 9730, 9732, 9809, 10138, 10149, 10157, 11099, 11257, 11258, 11487, 11532, 11558, 11578, 11634, 11653, 11668, 11697, 11724, 11781, 11799, 11820, 11837, 11857, 11869, 11892, 11895, 11901, 11945, 11947, 11952, 11987, 12052, 12083, 12158, 12178, 12200, 12346, 12350, 12393, 12420, 12432, 12445, 12449, 12453, 12454, 12460, 12469, 12489, 12509, 12510, 12511, 12518, 12527, 12541, 12545, 12551, 12582, 12583, 12587, 12597, 12601, 12611, 12625, 12626, 12631, 12650, 12653, 12655, 12660, 12671, 12681, 12684, 12685, 12711, 12713, 12714, 12717, 12723, 12724, 12734, 12738, 12746, 12766, 12775, 12777, 12782, 12788, 12792, 12795, 12811, 12813, 12814, 12841 * New Linux interfaces: clock_adjtime, name_to_handle_at, open_by_handle_at, syncfs, setns, sendmmsg * New locales: os_RU, bem_ZA, en_ZA, ff_SN, sw_KE, sw_TZ, lb_LU, wae_CH, yue_HK, lij_IT, mhr_RU * New encodings: CP770, CP771, CP772, CP773, CP774 * New program sotruss to trace calls through PLTs Implemented by Ulrich Drepper. * The malloc hook implementation is marked deprecated and will be removed from the default implementation in the next version. The design never worked ever since the introduction of threads. Even programs which do not create threads themselves can use multiple threads created internally. I don't expect any program breakage but if you notice some, tell me, please! Andreas -- Andreas Jaeger, Program Manager openSUSE aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday, August 18, 2011 09:16:50 Andreas Jaeger wrote:
I've submitted yesterday glibc 2.14 to Base:System and was surprised that all packages build fine there.
The new glibc is now in Factory, Andreas -- Andreas Jaeger, Program Manager openSUSE aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
* Andreas Jaeger <aj@suse.com> [2011-08-18 09:17]:
* The malloc hook implementation is marked deprecated and will be removed from the default implementation in the next version. The design never worked ever since the introduction of threads. Even programs which do not create threads themselves can use multiple threads created internally.
I don't expect any program breakage but if you notice some, tell me, please!
This broke zfs-fuse, to be more specific it broke the port of libumem that comes with it and I'm not sure I understand why the addition of an attribute causes malloc.c:456:8: error: conflicting type qualifiers for '__malloc_initialize_hook' /usr/include/malloc.h:170:38: note: previous declaration of '__malloc_initialize_hook' was here (for complete build logs see filesystems/zfs-fuse) Code in question is here: http://gitweb.zfs-fuse.net/?p=official;a=blob;f=src/lib/libumem/malloc.c;h=7... Any ideas on how to address this? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Guido Berhoerster <gber@opensuse.org> writes:
* Andreas Jaeger <aj@suse.com> [2011-08-18 09:17]:
* The malloc hook implementation is marked deprecated and will be removed from the default implementation in the next version. The design never worked ever since the introduction of threads. Even programs which do not create threads themselves can use multiple threads created internally.
I don't expect any program breakage but if you notice some, tell me, please!
This broke zfs-fuse, to be more specific it broke the port of libumem that comes with it and I'm not sure I understand why the addition of an attribute causes malloc.c:456:8: error: conflicting type qualifiers for '__malloc_initialize_hook' /usr/include/malloc.h:170:38: note: previous declaration of '__malloc_initialize_hook' was here (for complete build logs see filesystems/zfs-fuse)
Code in question is here: http://gitweb.zfs-fuse.net/?p=official;a=blob;f=src/lib/libumem/malloc.c;h=7...
Any ideas on how to address this?
The header was changed with two changes: * Adding the deprecated attribute * Giving a real definition for __MALLOC_HOOK_VOLATILE and thus I expect that the following will fix it: Replace: void (*__malloc_initialize_hook)(void) = umem_malloc_init_hook; With: void (*volatile __malloc_initialize_hook)(void) = umem_malloc_init_hook; But note, the whole interface is deprecated, so for glibc 2.15 this needs to be rewritten, Andreas -- Andreas Jaeger, aj@{novell.com,suse.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
* Andreas Jaeger <aj@suse.de> [2011-08-20 16:20]:
Guido Berhoerster <gber@opensuse.org> writes:
* Andreas Jaeger <aj@suse.com> [2011-08-18 09:17]:
* The malloc hook implementation is marked deprecated and will be removed from the default implementation in the next version. The design never worked ever since the introduction of threads. Even programs which do not create threads themselves can use multiple threads created internally.
I don't expect any program breakage but if you notice some, tell me, please!
This broke zfs-fuse, to be more specific it broke the port of libumem that comes with it and I'm not sure I understand why the addition of an attribute causes malloc.c:456:8: error: conflicting type qualifiers for '__malloc_initialize_hook' /usr/include/malloc.h:170:38: note: previous declaration of '__malloc_initialize_hook' was here (for complete build logs see filesystems/zfs-fuse)
Code in question is here: http://gitweb.zfs-fuse.net/?p=official;a=blob;f=src/lib/libumem/malloc.c;h=7...
Any ideas on how to address this?
The header was changed with two changes: * Adding the deprecated attribute * Giving a real definition for __MALLOC_HOOK_VOLATILE
and thus I expect that the following will fix it: Replace: void (*__malloc_initialize_hook)(void) = umem_malloc_init_hook;
With: void (*volatile __malloc_initialize_hook)(void) = umem_malloc_init_hook;
Thanks, I overlooked the second change.
But note, the whole interface is deprecated, so for glibc 2.15 this needs to be rewritten,
This could become a problematic since libumem uses these hooks to divert malloc, I haven't looked yet whether this is actually relied on, I'd assume that the Solaris code makes direct use of umem_alloc()/umem_zalloc(). -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Andreas Jaeger -
Andreas Jaeger -
Guido Berhoerster