gcc 3.0.x/glibc 2.2.4 policy

[Andreas Jaeger]

Ulrich Drepper <drepper@redhat.com> writes:

> Andreas Jaeger <aj@suse.de> writes:
>
>> Here's a patch for configure.in, what do you think?  I made this an
>> extra test that can be overwritten with --disable-sanity-checks.
>
> Looks good.  I assume you tested it?  If yes, go ahead.

I haven't tested it yet - but will do later today and commit it if it
works with all compilers I have on my machine (gcc 2.95, gcc 3.0, gcc
3.1).

Andreas
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7ckpxOJpWPMJyoSYRAglgAJ4txxmBRQuv4NVDvw0U6NRfThAScQCcDA2p
emVFZB6YB1kL6HRtfmahy4s=
=XGzT
-----END PGP SIGNATURE-----From drepper@redhat.com Thu Aug 09 01:58:00 2001
From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: today's work
Date: Thu, 09 Aug 2001 01:58:00 -0000
Message-id: <m3elql62em.fsf@otr.mynet>
X-SW-Source: 2001-08/msg00033.html
Content-length: 956

You might have seen that I checked in a substantial amount of changes
today.  I get results from a test suite which mostly are correct in
identifying problems.  It's unfortunate that it's so late but better
than never.  Tomorrow I have another full day of debugging ahead of me
and once this is done I fear we have enough changes to invalidate
previous results.

But since almost all the changes affect wide char streams and other
wide char functions I doubt that another test release will be of much
help.  Instead I think it's much better to simply have the
distribution makers run their tests (and builds) and see whether the
changes cause problems.

If you know of any applications using wide char functions please start
testing.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------