* Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional @ 2007-08-14 11:21 Christoph Conrad 2007-08-14 12:31 ` Jason Rumney 0 siblings, 1 reply; 17+ messages in thread From: Christoph Conrad @ 2007-08-14 11:21 UTC (permalink / raw) To: emacs-pretest-bug I _did_ nmake bootstrap. cp: Aufruf von stat für "obj-spd/i386/cmdproxy.exe" nicht möglich: No such file or directory NMAKE : fatal error U1077: 'cp': R³ckgabe-Code '0x1' (German messages) That means: cant call stat on "obj-spd/i386/cmdproxy.exe": No such file or directory ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 11:21 Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional Christoph Conrad @ 2007-08-14 12:31 ` Jason Rumney 2007-08-14 12:47 ` Christoph Conrad 0 siblings, 1 reply; 17+ messages in thread From: Jason Rumney @ 2007-08-14 12:31 UTC (permalink / raw) To: Christoph Conrad; +Cc: emacs-pretest-bug Christoph Conrad wrote: > I _did_ nmake bootstrap. > > cp: Aufruf von stat für "obj-spd/i386/cmdproxy.exe" nicht möglich: No such file > or directory > NMAKE : fatal error U1077: 'cp': R³ckgabe-Code '0x1' > > (German messages) That means: cant call stat on > "obj-spd/i386/cmdproxy.exe": No such file or directory > What version of Emacs are you trying to build? Have you built with that compiler before? When? At which stage in the compilation process does this happen? ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 12:31 ` Jason Rumney @ 2007-08-14 12:47 ` Christoph Conrad 2007-08-14 14:40 ` Jason Rumney 0 siblings, 1 reply; 17+ messages in thread From: Christoph Conrad @ 2007-08-14 12:47 UTC (permalink / raw) To: Jason Rumney; +Cc: emacs-pretest-bug Hi Jason, > What version of Emacs are you trying to build? Current CVS Version. > Have you built with that compiler before? When? Numerous times in the past since january. > At which stage in the compilation process does this happen? Messages directly before the error message: ============================================================ Finding pointers to doc strings... Finding pointers to doc strings...done Dumping under the name emacs Dumping from d:/user/cco/emacs-cvs/src/obj-spd/i386/temacs.exe to d:/user/cco/emacs-cvs/src/obj-spd/i386/emacs.exe 68703 pure bytes used mkdir "../bin" Subdirectory or file with name "../bin" already exists. cp -f obj-spd/i386/emacs.exe ../bin nmake bootstrap-clean Microsoft (R) Program Maintenance Utility, Version 7.10.3077 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. rm obj-spd/i386/alloc.obj rm obj-spd/i386/data.obj rm obj-spd/i386/intervals.obj rm obj-spd/i386/keyboard.obj rm obj-spd/i386/keymap.obj cp -f obj-spd/i386/cmdproxy.exe ../bin ============================================================ Commands executed in cmd.exe-Shell: - vcvars32 - .\configure --with-msvc --without-xpm --without-png --without-jpeg \ --without-tiff --without-gif - nmake bootstrap Best regards, Christoph ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 12:47 ` Christoph Conrad @ 2007-08-14 14:40 ` Jason Rumney 2007-08-14 15:19 ` dhruva 2007-08-15 7:42 ` Christoph Conrad 0 siblings, 2 replies; 17+ messages in thread From: Jason Rumney @ 2007-08-14 14:40 UTC (permalink / raw) To: Christoph Conrad; +Cc: emacs-pretest-bug Christoph Conrad wrote: > Hi Jason, > > >> What version of Emacs are you trying to build? >> > > Current CVS Version. > Strange, the following change should have fixed this exact bug: 2007-07-16 Eli Zaretskii <eliz@gnu.org> * makefile.w32-in (bootstrap, bootstrap-nmake, bootstrap-gmake): Depend on cmdproxy. Does nmake have any debug flags that show what commands are being run when, so you can debug this? ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 14:40 ` Jason Rumney @ 2007-08-14 15:19 ` dhruva 2007-08-14 15:28 ` dhruva 2007-08-15 7:42 ` Christoph Conrad 1 sibling, 1 reply; 17+ messages in thread From: dhruva @ 2007-08-14 15:19 UTC (permalink / raw) To: Jason Rumney; +Cc: emacs-pretest-bug, Christoph Conrad Hi, On 8/14/07, Jason Rumney <jasonr@gnu.org> wrote: > Christoph Conrad wrote: > > Hi Jason, > > > > > >> What version of Emacs are you trying to build? > >> > > > > Current CVS Version. > > > > Strange, the following change should have fixed this exact bug: > > 2007-07-16 Eli Zaretskii <eliz@gnu.org> > > * makefile.w32-in (bootstrap, bootstrap-nmake, bootstrap-gmake): > Depend on cmdproxy. > > > Does nmake have any debug flags that show what commands are being run > when, so you can debug this? I can confirm the bootstrap failure using VC 2003. The strange part is that the 'cp' of cmdproxy.exe is called and cmdproxy.exe is available in the folder but fails to get copied to 'bin' folder. I am trying to debug as I have both MinGW and VC build environment. -------------- E:\cache\build\emacs\nt [dky]nmake /NOLOGO /N bootstrap cd ..\lisp nmake bootstrap-clean cd ..\src nmake clean cd ..\lib-src nmake clean cd ..\src nmake bootstrap nmake bootstrap-clean cp -f obj-spd/i386/cmdproxy.exe ../bin cd ..\lisp nmake SHELL=CMD bootstrap cd ..\lib-src nmake DOC cd ..\nt nmake all ------------- -dky -- Dhruva Krishnamurthy Contents reflect my personal views only! ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 15:19 ` dhruva @ 2007-08-14 15:28 ` dhruva 2007-08-14 15:39 ` Jason Rumney 2007-08-15 8:12 ` Christoph Conrad 0 siblings, 2 replies; 17+ messages in thread From: dhruva @ 2007-08-14 15:28 UTC (permalink / raw) To: Jason Rumney; +Cc: emacs-pretest-bug, Christoph Conrad Hi, I found the problem. We need to change back to the 'nt' folder. The following patch fixes the issue. -dky *** emacs.3661d004ffb8\nt\makefile.w32-in 2007-08-14 20:56:41.218750000 +0530 --- E:\cache\build\emacs\nt\makefile.w32-in 2007-08-14 20:56:27.156250000 +0530 *************** bootstrap-nmake: addsection cmdproxy *** 153,158 **** --- 153,159 ---- cd ..\src $(MAKE) $(MFLAGS) bootstrap $(MAKE) $(MFLAGS) bootstrap-clean + cd ..\nt $(CP) $(BLD)/cmdproxy.exe ../bin cd ..\lisp $(MAKE) $(MFLAGS) SHELL=$(SHELLTYPE) bootstrap -- Dhruva Krishnamurthy Contents reflect my personal views only! ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 15:28 ` dhruva @ 2007-08-14 15:39 ` Jason Rumney 2007-08-14 16:43 ` dhruva 2007-08-15 8:12 ` Christoph Conrad 1 sibling, 1 reply; 17+ messages in thread From: Jason Rumney @ 2007-08-14 15:39 UTC (permalink / raw) To: dhruva; +Cc: emacs-pretest-bug, Christoph Conrad Thanks. I've checked it in to the release branch, it should flow through to the other branches as the syncs are done. dhruva wrote: > Hi, > I found the problem. We need to change back to the 'nt' folder. The > following patch fixes the issue. > > -dky > > > *** emacs.3661d004ffb8\nt\makefile.w32-in 2007-08-14 > 20:56:41.218750000 +0530 > --- E:\cache\build\emacs\nt\makefile.w32-in 2007-08-14 > 20:56:27.156250000 +0530 > *************** bootstrap-nmake: addsection cmdproxy > *** 153,158 **** > --- 153,159 ---- > cd ..\src > $(MAKE) $(MFLAGS) bootstrap > $(MAKE) $(MFLAGS) bootstrap-clean > + cd ..\nt > $(CP) $(BLD)/cmdproxy.exe ../bin > cd ..\lisp > $(MAKE) $(MFLAGS) SHELL=$(SHELLTYPE) bootstrap > > ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 15:39 ` Jason Rumney @ 2007-08-14 16:43 ` dhruva 2007-08-14 19:33 ` Eli Zaretskii 2007-08-14 20:01 ` Jason Rumney 0 siblings, 2 replies; 17+ messages in thread From: dhruva @ 2007-08-14 16:43 UTC (permalink / raw) To: Jason Rumney; +Cc: emacs-pretest-bug Hi, Another small problem I noticed. Using MinGW build, after a bootstrap, the emacs.exe under the 'bin' folder gets deleted. This happens for the bootstrap target under 'lisp' folder. Due to this, a later 'make recompile' fails. I propose not deleting the emacs.exe from the 'bin' folder. diff -r 3661d004ffb8 lisp/makefile.w32-in --- a/lisp/makefile.w32-in Mon Aug 13 13:40:47 2007 +0000 +++ b/lisp/makefile.w32-in Tue Aug 14 22:09:24 2007 +0530 @@ -396,7 +396,6 @@ bootstrap-clean-SH: # it will not be mistaken for an installed binary. bootstrap: update-subdirs autoloads mh-autoloads compile finder-data custom-deps - - $(DEL) "$(EMACS)" # # Assuming INSTALL_DIR is defined, copy the elisp files to it -- Dhruva Krishnamurthy Contents reflect my personal views only! ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 16:43 ` dhruva @ 2007-08-14 19:33 ` Eli Zaretskii 2007-08-15 1:03 ` dhruva 2007-08-14 20:01 ` Jason Rumney 1 sibling, 1 reply; 17+ messages in thread From: Eli Zaretskii @ 2007-08-14 19:33 UTC (permalink / raw) To: dhruva; +Cc: emacs-pretest-bug, jasonr > Date: Tue, 14 Aug 2007 22:13:22 +0530 > From: dhruva <dhruvakm@gmail.com> > Cc: emacs-pretest-bug@gnu.org > > Hi, > Another small problem I noticed. Using MinGW build, after a > bootstrap, the emacs.exe under the 'bin' folder gets deleted. This > happens for the bootstrap target under 'lisp' folder. Due to this, a > later 'make recompile' fails. I propose not deleting the emacs.exe > from the 'bin' folder. Please describe the sequence of commands that causes the recompile target to be run during bootstrap after deleting bin/emacs.exe. I don't see the recompile target anywhere in the list of targets or commands run as part of "make bootstrap" in the lisp subdirectory. What am I missing? ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 19:33 ` Eli Zaretskii @ 2007-08-15 1:03 ` dhruva 2007-08-15 3:19 ` Eli Zaretskii 0 siblings, 1 reply; 17+ messages in thread From: dhruva @ 2007-08-15 1:03 UTC (permalink / raw) To: Eli Zaretskii; +Cc: emacs-pretest-bug, jasonr Hi, On 8/15/07, Eli Zaretskii <eliz@gnu.org> wrote: > don't see the recompile target anywhere in the list of targets or > commands run as part of "make bootstrap" in the lisp subdirectory. > What am I missing? Apologies for not providing the complete information. When I keep updating from CVS/HG repo, I do an explicit 'recompile'. It does not get called by any top level 'bootstrap'. Earlier, I used to copy the emacs.exe again into the 'bin' folder. An alternative would be to use the emacs.exe in the $BLD folder. This can avoid the extra copy into the 'bin' folder. Anyway, this is just a trivial inconvenience issue, we could live with out any change though. -dky -- Dhruva Krishnamurthy Contents reflect my personal views only! ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-15 1:03 ` dhruva @ 2007-08-15 3:19 ` Eli Zaretskii 2007-08-15 8:19 ` dhruva 0 siblings, 1 reply; 17+ messages in thread From: Eli Zaretskii @ 2007-08-15 3:19 UTC (permalink / raw) To: dhruva; +Cc: emacs-pretest-bug, jasonr > Date: Wed, 15 Aug 2007 06:33:48 +0530 > From: dhruva <dhruvakm@gmail.com> > Cc: jasonr@gnu.org, emacs-pretest-bug@gnu.org > > Apologies for not providing the complete information. When I keep > updating from CVS/HG repo, I do an explicit 'recompile'. In that case, there should be no problem. After a "make bootstrap", you are supposed to run "make install", which copies the dumped emacs.exe into bin. And if you run "make recompile" after syncing with CVS and "make" rebuilds emacs.exe, just say this: make recompile EMACS=../src/oo-spd/i386/emacs.exe As Jason pointed out it is wrong to leave bootstrap emacs.exe around, but the subsequent "make install" should solve that. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-15 3:19 ` Eli Zaretskii @ 2007-08-15 8:19 ` dhruva 2007-08-15 18:07 ` Eli Zaretskii 0 siblings, 1 reply; 17+ messages in thread From: dhruva @ 2007-08-15 8:19 UTC (permalink / raw) To: Eli Zaretskii; +Cc: emacs-pretest-bug, jasonr Hi, On 8/15/07, Eli Zaretskii <eliz@gnu.org> wrote: > make recompile EMACS=../src/oo-spd/i386/emacs.exe Is it possible (technically) to use the emacs in the BLD folder instead of the one under 'bin'? The emacs executable will be always under the BLD folder before a call to 'recompile', am I right in this assumption? -dky -- Dhruva Krishnamurthy Contents reflect my personal views only! ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-15 8:19 ` dhruva @ 2007-08-15 18:07 ` Eli Zaretskii 2007-08-16 2:55 ` dhruva 0 siblings, 1 reply; 17+ messages in thread From: Eli Zaretskii @ 2007-08-15 18:07 UTC (permalink / raw) To: dhruva; +Cc: emacs-pretest-bug, jasonr > Date: Wed, 15 Aug 2007 13:49:22 +0530 > From: dhruva <dhruvakm@gmail.com> > Cc: jasonr@gnu.org, emacs-pretest-bug@gnu.org > > On 8/15/07, Eli Zaretskii <eliz@gnu.org> wrote: > > make recompile EMACS=../src/oo-spd/i386/emacs.exe > > Is it possible (technically) to use the emacs in the BLD folder > instead of the one under 'bin'? Yes. That's exactly what the command I show above does. emacs.exe in the BLD directory is a normal dumped Emacs, it's just not installed in `bin', and, possibly, didn't yet pick up all the latest doc strings due to modified Lisp files. "make install" handles both of these issues, but for compiling Lisp files, emacs.exe in BLD is usually good enough. > The emacs executable will be always under the BLD folder before a > call to 'recompile', am I right in this assumption? "make recompile" doesn't do anything with emacs.exe, so I'm unsure what you are asking here. In any case, if bin/emacs.exe is up to date, it's better to use it than src/oo-spd/i386/emacs.exe, because the former is guaranteed to have all the latest changes in doc strings and have all the latest Lisp files preloaded into it. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-15 18:07 ` Eli Zaretskii @ 2007-08-16 2:55 ` dhruva 0 siblings, 0 replies; 17+ messages in thread From: dhruva @ 2007-08-16 2:55 UTC (permalink / raw) To: Eli Zaretskii; +Cc: emacs-pretest-bug, jasonr Hi, On 8/15/07, Eli Zaretskii <eliz@gnu.org> wrote: > "make recompile" doesn't do anything with emacs.exe, so I'm unsure > what you are asking here. It is just for the sake of completeness. On a default build setup using MinGW, if I do a 'make recompile', it fails. I need to send the extra arguments (as suggested by you) or copy the emacs.exe to the 'bin' folder. Using emacs.exe in the BLD folder by default would ensure default call 'make recompile' succeed. IMHO, the 'recompile' target is required in the development environment to compile the updated lisp files. with best regards, dhruva -- Dhruva Krishnamurthy Contents reflect my personal views only! ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 16:43 ` dhruva 2007-08-14 19:33 ` Eli Zaretskii @ 2007-08-14 20:01 ` Jason Rumney 1 sibling, 0 replies; 17+ messages in thread From: Jason Rumney @ 2007-08-14 20:01 UTC (permalink / raw) To: dhruva; +Cc: emacs-pretest-bug ]}]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]#dhruva wrote: > Hi, > Another small problem I noticed. Using MinGW build, after a > bootstrap, the emacs.exe under the 'bin' folder gets deleted. If it only happens with a mingw build, then it is a problem with the msvc build. The emacs.exe used for bootstrapping is dumped with uncompiled lisp files, so it is deleted deliberately. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 15:28 ` dhruva 2007-08-14 15:39 ` Jason Rumney @ 2007-08-15 8:12 ` Christoph Conrad 1 sibling, 0 replies; 17+ messages in thread From: Christoph Conrad @ 2007-08-15 8:12 UTC (permalink / raw) To: emacs-devel; +Cc: emacs-pretest-bug Hi, > We need to change back to the 'nt' folder. The following patch fixes > the issue. I can confirm that. Thank you very much! Best regards, Christoph ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional 2007-08-14 14:40 ` Jason Rumney 2007-08-14 15:19 ` dhruva @ 2007-08-15 7:42 ` Christoph Conrad 1 sibling, 0 replies; 17+ messages in thread From: Christoph Conrad @ 2007-08-15 7:42 UTC (permalink / raw) To: Jason Rumney; +Cc: emacs-pretest-bug Hi Jason, > Does nmake have any debug flags that show what commands are being run > when, so you can debug this? nmake /D should do this, but unfortunately it does not do what it should. Strange. Can not investigate further this week. Best regards, Christoph ^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2007-08-16 2:55 UTC | newest] Thread overview: 17+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2007-08-14 11:21 Bootstrapping CVS Emacs fails with VC 2003 on Windows XP Professional Christoph Conrad 2007-08-14 12:31 ` Jason Rumney 2007-08-14 12:47 ` Christoph Conrad 2007-08-14 14:40 ` Jason Rumney 2007-08-14 15:19 ` dhruva 2007-08-14 15:28 ` dhruva 2007-08-14 15:39 ` Jason Rumney 2007-08-14 16:43 ` dhruva 2007-08-14 19:33 ` Eli Zaretskii 2007-08-15 1:03 ` dhruva 2007-08-15 3:19 ` Eli Zaretskii 2007-08-15 8:19 ` dhruva 2007-08-15 18:07 ` Eli Zaretskii 2007-08-16 2:55 ` dhruva 2007-08-14 20:01 ` Jason Rumney 2007-08-15 8:12 ` Christoph Conrad 2007-08-15 7:42 ` Christoph Conrad
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs.git 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).