MySQL Bugs: #39996: 5.1 fails to compile on Windows 32-bit with VS2005

Bug #39996	5.1 fails to compile on Windows 32-bit with VS2005
Submitted:	13 Oct 2008 11:54	Modified:	16 Feb 2010 12:22
Reporter:	Miguel Solorzano	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S2 (Serious)
Version:	5.1	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Compiling process fails with the below error message:

Generating sql_yacc.h
bison.exe: option `--defines' doesn't allow an argument
Usage: bison.exe [-dhklntvyV] [-b file-prefix] [-o outfile] [-p name-prefix]
       [--debug] [--defines] [--fixed-output-files] [--no-lines]
       [--verbose] [--version] [--help] [--yacc]
       [--no-parser] [--token-table]
       [--file-prefix=prefix] [--name-prefix=prefix]
       [--output=outfile] grammar-file
Report bugs to bug-bison@gnu.org
Project : error PRJ0019: A tool returned an error code from "Generating sql_yacc.h"
Build log was saved at "file://c:\build\mysql-5.1\sql\mysqld.dir\Debug\BuildLog.htm"
mysqld - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 2 failed, 22 up-to-date, 0 skipped ==========

C:\build\mysql-5.1>bison --version
bison (GNU Bison) 2.1
Written by Robert Corbett and Richard Stallman.

Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

VS2003 not presents this compile problem.

How to repeat:
see description

Suggested fix:
-

Bison should not be required *at all* to build from our source distributions. It is possible that a damaged source tree or one with broken timestamps (such as from copying an extracted source tree or extracting the source archive with a tool that doesn't preserve timestamps, or a skewed clock on the build machine) causes a rebuild of the parser, in which case bison 2.1 is apparently too old. Newer bison versions accept an option to --defines.

We don't see this problem in pushbuild (VS2005) or in release builds.

See note above - ok to close as not a bug?

Yes it is ok to close as can't repeat and !bug I am not sure however you decide.