public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mark@moxienet.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/7126: zlib version is wrong in zlib/configure.in
Date: Tue, 25 Jun 2002 15:26:00 -0000 [thread overview]
Message-ID: <20020625205645.24664.qmail@sources.redhat.com> (raw)
>Number: 7126
>Category: bootstrap
>Synopsis: zlib version is wrong in zlib/configure.in
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jun 25 14:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Mark Mentovai
>Release: 3.1 and gcc-3_1-branch 3.1.1 20020625 (prerelease)
>Organization:
>Environment:
System: SunOS s7 5.8 Generic_108528-15 sun4u sparc SUNW,UltraAX-i2
Architecture: sun4
Sun Netra T1 200, 500MHz UltraSPARC IIe, 1GB, 2x18GB
Sun Solaris 7/01 MU 7
host: sparc-sun-solaris2.8
build: sparc-sun-solaris2.8
target: sparc-sun-solaris2.8
configured with: ../gcc-3.1-20020620/configure --enable-shared --with-gnu-as --with-gnu-ld --enable-threads --with-cpu=ultrasparc --enable-libgcj --with-system-zlib
>Description:
The zlib sources supplied with gcc are now version 1.1.4. zlib/configure.in has yet to be notified of this change, and still believes that it is configuring version 1.1.3. Messages during the build process lead the user to believe that version 1.1.3 is in use, this can be frightening if the user is aware of the double-free vulnerability in 1.1.3 as described at http://www.gzip.org/zlib/advisory-2002-03-11.txt .
>How-To-Repeat:
>Fix:
zlib/configure.in:38:
AM_INIT_AUTOMAKE(zlib, 1.1.4)
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-06-25 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 15:26 mark [this message]
2003-05-14 9:16 Dara Hazeghi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020625205645.24664.qmail@sources.redhat.com \
--to=mark@moxienet.com \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).