This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/12044] GLIBC compiling with ERR
- From: "lshulov at arabellasw dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Aug 2003 08:32:39 -0000
- Subject: [Bug other/12044] GLIBC compiling with ERR
- References: <20030824075411.12044.lshulov@arabellasw.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12044
------- Additional Comments From lshulov at arabellasw dot com 2003-08-25 08:32 -------
Subject: Re: GLIBC compiling with ERR
aj at gcc dot gnu dot org wrote:
>PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
>
>http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12044
>
>
>aj at gcc dot gnu dot org changed:
>
> What |Removed |Added
>----------------------------------------------------------------------------
> Status|WAITING |RESOLVED
> Resolution| |INVALID
>
>
>------- Additional Comments From aj at gcc dot gnu dot org 2003-08-25 06:43 -------
>This is a bug in glibc triggered by newer GCCs:
>
>scanf.c: In function `sscanf':
>sscanf.c:37: error: `va_start' used in function with fixed args
>
>Change the declaration of stdio-common/sscanf.c to:
>int
>sscanf (const char *s, const char *format, ...)
>
>This is fixed in the development version of glibc already but the latest
>release (2.3.2) has this bug.
>
>Closing since this is not a GCC bug.
>
>
>
>------- You are receiving this mail because: -------
>You reported the bug, or are watching the reporter.
>
>
>
Thank you. It's work
Leonid