bug#689: Byte-compiler failures building from CVS on Windows XP

[ＯＦＦＩＣＥ ZERO]

Do not send any mail1!
no thank you!!





----- Original Message ----- 
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: "Francis Litterio" <flitterio@gmail.com>; 
<689@emacsbugs.donarmstrong.com>
Cc: <bug-gnu-emacs@gnu.org>
Sent: Monday, August 11, 2008 7:35 AM
Subject: bug#689: Byte-compiler failures building from CVS on Windows XP


Francis Litterio wrote:
> When building Emacs from CVS on Windows XP SP2 using Visual Studio 6.0,
> I'm seeing strange failures when byte-compiling the Elisp files.  Here
> are a couple of examples:
>
> c:\franl\cvs\emacs\lisp>"c:\franl\cvs\emacs\lisp/../bin/emacs.exe" -batch  
> --no-init-file --no-site-file --multibyte -l loaddefs -f 
> batch-byte-compile-if-not-done gnus/legacy-gnus-agent.el
> In toplevel form:
> gnus/legacy-gnus-agent.el:28:1:Error: Symbol's value as variable is void: 
> �d

Building my patched version with gcc today I did not seee this.

> c:\franl\cvs\emacs\lisp>"c:\franl\cvs\emacs\lisp/../bin/emacs.exe" -batch  
> --no-init-file --no-site-file --multibyte -l loaddefs -f 
> batch-byte-compile-if-not-done gnus/nneething.el
> In toplevel form:
> gnus/nneething.el:32:1:Error: Symbol's value as variable is void: �����y

Neither this.

> Is anyone else seeing this?  This didn't happen when I built from CVS a
> few months ago.
> --
> Fran