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

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

[Francis Litterio]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 868 bytes --]

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

	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

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

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

[Lennart Borgman (gmail)]

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
> 
> 
> 
> 
> 
> 

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
>
>
>
>
>
>

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
>
>
>
>
>
>

bug#689: Info received (bug#689: Byte-compiler failures building from CVS on Windows XP)

[ＯＦＦＩＣＥ ZERO]

Do not send me any mail !
No thank you　！！

----- Original Message ----- 
From: "Emacs bug Tracking System" <don@donarmstrong.com>
To: "ＯＦＦＩＣＥ　ZERO" <hi-oh230@air.ocn.ne.jp>
Sent: Monday, August 11, 2008 10:00 AM
Subject: bug#689: Info received (bug#689: Byte-compiler failures building 
from CVS on Windows XP)



Thank you for the additional information you have supplied regarding
this bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Emacs Bugs <bug-gnu-emacs@gnu.org>

If you wish to submit further information on this problem, please
send it to 689@emacsbugs.donarmstrong.com, as before.

Please do not send mail to don@donarmstrong.com unless you wish
to report a problem with the Bug-tracking system.


-- 
689: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=689
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems 

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

[ＯＦＦＩＣＥ ZERO]

Do not send any mail !
no thank you



----- Original Message ----- 
From: "Francis Litterio" <flitterio@gmail.com>
To: <bug-gnu-emacs@gnu.org>
Sent: Monday, August 11, 2008 6:53 AM
Subject: bug#689: Byte-compiler failures building from CVS on Windows XP


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

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

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