building glibc 2.15

Allin Cottrell cottrell@wfu.edu
Fri Mar 23 19:59:00 GMT 2012


On Thu, 22 Mar 2012, Mike Frysinger wrote:

> On Thursday 22 March 2012 17:10:18 Allin Cottrell wrote:
>> On Thu, 22 Mar 2012, Mike Frysinger wrote:
>>> On Thursday 22 March 2012 12:46:01 Allin Cottrell wrote:
>>>> Thanks. After I applied the __i686 patch found on the wiki
>>>> glibc 2.15 built OK. But I'm seeing a few failures on "make
>>>> check" and wondered if they were "expected" or anomalous. The
>>>> failed tests are tst-mqueue1, tst-mqueue2, tst-mqueue3,
>>>> tst-mqueue4, tst-mqueue7 and check-localplt. I can post the
>>>> .out files if that's useful, but for example:
>>>>
>>>> "mq_setattr on invalid mqd_t did not fail with EBADF: \
>>>> Function not implemented"
>>>>
>>>> "fct: mq_getattr failed: Function not implemented"
>>>>
>>>> This is on Linux 3.3, gcc 4.7.0.
>>>
>>> but what version of kernel headers are you building against ?
>>
>> The headers are from 3.3. But -- maybe this is the issue -- I
>> followed Linus's suggestion a little while back and built a
>> 64-bit kernel, though the rest of the system is i686. (So when
>> I configured glibc I used --build=i686-pc-linux-gnu.)
>>
>> Hmm, in this situation is it necessary to configure the
>> "public" kernel headers as i686? Well, I can google.
>
> the exported kernel headers don't have autoconf style options, and the
> x86_64/x86 headers are unified, so that shouldn't matter.

Thanks. Given the "check" failures I thought I'd try using 
slightly more conservative kernel headers -- 3.2.12 instead of 
3.3. Now make check gives fewer fails: just tst-mqueue5 and 
check-localplt. The messages are

tst-mqueue5.out:
SIGRTMIN signal in child did not arrive
child failed with status 256

check-localplt.out:
--- ../scripts/data/localplt-i386-linux-gnu.data 
2012-01-01 07:16:32.000000000 -0500
+++ -   2012-03-23 15:26:52.785977398 -0400
@@ -4,4 +4,5 @@
  libc.so: malloc
  libc.so: memalign
  libc.so: realloc
+libm.so: feraiseexcept
  libm.so: matherr

Any judgment on whether these are things to worry about?
Thanks.

Allin Cottrell



More information about the Libc-help mailing list