This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.18 freeze!
- From: Adhemerval Zanella <azanella at linux dot vnet dot ibm dot com>
- To: libc-alpha at sourceware dot org
- Date: Thu, 13 Jun 2013 10:16:31 -0300
- Subject: Re: glibc 2.18 freeze!
- References: <51ACFE36 dot 5000603 at redhat dot com> <CAAKybw9ZuOKSpXgCGb5mFVHkKmrnUCKAdStg+i7+_ckUM9Qp2g at mail dot gmail dot com> <51ADFC0B dot 1060907 at linux dot vnet dot ibm dot com> <20130611183029 dot B62D52C0A2 at topped-with-meat dot com> <51B78382 dot 6000403 at linux dot vnet dot ibm dot com> <20130611213211 dot EA4E12C09F at topped-with-meat dot com> <51B893F9 dot 6010401 at linux dot vnet dot ibm dot com> <Pine dot LNX dot 4 dot 64 dot 1306130010000 dot 9276 at digraph dot polyomino dot org dot uk> <20130613100700 dot GR19582 at spoyarek dot pnq dot redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1306131242270 dot 10141 at digraph dot polyomino dot org dot uk> <51B9C3F3 dot 2070309 at linux dot vnet dot ibm dot com>
On 13-06-2013 10:06, Adhemerval Zanella wrote:
> On 13-06-2013 09:42, Joseph S. Myers wrote:
>> On Thu, 13 Jun 2013, Siddhesh Poyarekar wrote:
>>
>>> I don't see this in any of my tests with gcc-4.7.2 or with 4.8, with
>>> or without -O3 in CFLAGS. Did you do a clean build? In fact the
>> Yes, this failure is with a clean build.
>>
> I could reproduce it here in my environment and I am trying to figure out
> why on PPC32/PPC64 and some x86_64 builds the rtld-xxx objects have
> '-DNOT_IN_libc=1 -DIS_IN_rtld=1 -DIN_LIB=rtld' defines while on this x86_64
> I have setup they are not present. I added a guard in my patch to prevent
> to use the alias for loader objects (!defined NOT_IN_libc) to exactly avoid
> this kind of issue.
>
In fact are just some objects: sysdeps/x86_64/multiarch/rtld-memcmp.c and
sysdeps/x86_64/rtld-memset.c.