This is the mail archive of the
libc-hacker@cygnus.com
mailing list for the glibc project.
Re: ["Carlos Wijders" <computec@sr.net>] libc/968: 'make check' fails with glibc-2.1
- To: Andreas Jaeger <aj@arthur.rhein-neckar.de>
- Subject: Re: ["Carlos Wijders" <computec@sr.net>] libc/968: 'make check' fails with glibc-2.1
- From: Zack Weinberg <zack@rabi.columbia.edu>
- Date: Wed, 17 Feb 1999 12:26:35 -0500
- cc: libc-hacker@cygnus.com
On 17 Feb 1999 17:55:53 +0100, Andreas Jaeger wrote:
>>>>>> Zack Weinberg writes:
>>>
>>> The problem is not running those binaries but compiling them!
>>>
>>> The glibc2 FAQ advises to move /usr/include away when upgrading from
>>> libc5 to glibc2 - and if you do so, make check will fail since those
>>> two binaries can't be *compiled*. If they could be compiled, there
>>> wouldn't be a problem.
>
>ZW> This mess is fixed in my revised test framework. The header tests are
>ZW> compiled without reference to the system headers, and examine only the
>ZW> headers provided by the just-built libc plus the compiler's headers.
>
>Sounds fine!
>
>Ok, then let's change the thread;-) : When and how should your revised
>framework be added to glibc 2.1?
I don't think it can be done for 2.1. It's the second thing on my list
for 2.2, after the build patch I had last summer that didn't get in.
zw