[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: make check fails on linuxthreads
From: |
Andreas Jaeger |
Subject: |
Re: make check fails on linuxthreads |
Date: |
Thu, 09 Aug 2001 12:32:02 +0200 |
User-agent: |
Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Artificial Intelligence) |
Michiel Uitdehaag <address@hidden> writes:
> Hi,
>
> I just downloaded glibc-2.2.3 and am unable to complete 'make check'.
>
> Environment:
> Host type: i686-pc-linux-gnu (AMD Athlon 600)
> System: Linux 2.4.5
There's a kernel bug in 2.4.5 that might explain this (a race).
> Architecture: i686
> Addons: linuxthreads
> Build CC: gcc
> Compiler version: 2.95.3
> Kernel headers: 2.4.5
>
> I untarred the package in /usr/local/packages/glibc-2.2.3/
> I untarred the linuxthreads tar inside the glibc-2.2.3 directory
> I build in /usr/local/packages/glibc-2.2.3-build/
> Configure was invoked with --prefix=/usr --enable-add-ons
> --enable-kernel=2.4.5
Try again with --enable-kernel=2.3.99,
Andreas
> make completed without problems
> make check fails for the linuxthreads ex1 check:
> GCONV_PATH=/usr/local/packages/glibc-2.2.3-build/iconvdata LC_ALL=C
> /usr/local/packages/glibc-2.2.3-build/elf/ld-linux.so.2 --library-path
> /usr/local/packages/glibc-2.2.3-build:/usr/local/packages/glibc-2.2.3-build/math:/usr/local/packages/glibc-2.2.3-build/elf:/usr/local/packages/glibc-2.2.3-build/dlfcn:/usr/local/packages/glibc-2.2.3-build/nss:/usr/local/packages/glibc-2.2.3-build/nis:/usr/local/packages/glibc-2.2.3-build/rt:/usr/local/packages/glibc-2.2.3-build/resolv:/usr/local/packages/glibc-2.2.3-build/crypt:/usr/local/packages/glibc-2.2.3-build/linuxthreads
> /usr/local/packages/glibc-2.2.3-build/linuxthreads/ex1
>
> with output:
>
> create a failed 11
> create b failed 11
> join a failed 3
> join b failed 3
>
> If I run the ex1 executable by hand as ./ex1, the output is presumably
> correct (lots of a's and b's).
>
> I checked the GNATS database and found bug report 2200 on this subject.
> However, I cannot find if and how this problem has been resolved.
>
> Any information you can provide will be much appreciated.
>
> Kind regards,
--
Andreas Jaeger
SuSE Labs address@hidden
private address@hidden
http://www.suse.de/~aj