unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* Building Emacs on MS Windows
@ 2003-02-05 23:16 Lars Hansen
  2003-02-05 23:29 ` Juanma Barranquero
  2003-02-06  5:55 ` Eli Zaretskii
  0 siblings, 2 replies; 3+ messages in thread
From: Lars Hansen @ 2003-02-05 23:16 UTC (permalink / raw)


I have some problems building Emacs from CVS on MS Windows.

1. It seems the files nt/configure.bat and nt/makefile.w32-in have wrong 
newlines.

2. When I correct this and try the command "configure.bat" followed by 
mingw32-make.exe bootstrap" in the nt directory, I get a lot of errors like:

 >>Error occurred processing calc/calc-aent.el: File error (("Opening 
input file" "no such file or directory" 
"d:/cvs/emacs/nt/calc/calc-aent.el"))

Obviosly the problem is that the directory calc resides in the directory 
lisp rather than in the directory nt. I have tried in the file 
lisp/makefile to prefix each module name in the variable WINS with 
"$(lisp)/". That seems to get me past the problem above. But then I get 
the following error:

mingw32-make.exe[1]: Entering directory `D:/cvs/emacs/leim'
"./../src/oo-spd/i386/emacs.exe" -batch --no-init-file --no-site-file 
--multibyte -l D:/cvs/emacs/leim/../lisp/international/titdic-cnv \
     --eval '(batch-titdic-convert t)' \
     -dir quail ./CXTERM-DIC
Converting d:/cvs/emacs/nt/CXTERM-DIC to quail-package...
Opening input file: no such file or directory, d:/cvs/emacs/nt/CXTERM-DIC
Signal 127
mingw32-make.exe[1]: *** [quail/CCDOSPY.elc] Error 255
mingw32-make.exe[1]: Leaving directory `D:/cvs/emacs/leim'
d:\mingw\bin\mingw32-make.exe: *** [all-other-dirs-gmake] Error 2

Obviosly the problem is the directory CXTERM-DIC resides in the 
directory leim rather than in the directory nt.

What is wrong here?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Building Emacs on MS Windows
  2003-02-05 23:16 Building Emacs on MS Windows Lars Hansen
@ 2003-02-05 23:29 ` Juanma Barranquero
  2003-02-06  5:55 ` Eli Zaretskii
  1 sibling, 0 replies; 3+ messages in thread
From: Juanma Barranquero @ 2003-02-05 23:29 UTC (permalink / raw)



On Thu, 06 Feb 2003 00:16:21 +0100
Lars Hansen <larsh@kabelnettet.dk> wrote:

> I have some problems building Emacs from CVS on MS Windows.
> 
> 1. It seems the files nt/configure.bat and nt/makefile.w32-in have wrong 
> newlines.

Yes.

Or, to be precise, I think the .bat files were commited to the CVS with
CR/LF pairs but weren't marked as binary... so many CVS clients, when
checking them out, blindly traslate CR/LF to CR/CR/LF. I usually do

  cvs -q update -C -kb *.bat

to get rid of the problem.

> 2. When I correct this and try the command "configure.bat" followed by 
> mingw32-make.exe bootstrap" in the nt directory, I get a lot of errors like:

Are you using bash?

-- 
Juanma Barranquero <lektu@terra.es>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Building Emacs on MS Windows
  2003-02-05 23:16 Building Emacs on MS Windows Lars Hansen
  2003-02-05 23:29 ` Juanma Barranquero
@ 2003-02-06  5:55 ` Eli Zaretskii
  1 sibling, 0 replies; 3+ messages in thread
From: Eli Zaretskii @ 2003-02-06  5:55 UTC (permalink / raw)
  Cc: bug-gnu-emacs


On Thu, 6 Feb 2003, Lars Hansen wrote:

> I have some problems building Emacs from CVS on MS Windows.

Please don't report problems with CVS versions of Emacs here.  Instead, 
please use the mailing list emacs-pretest-bug@gnu.org.

Thanks.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-02-06  5:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-02-05 23:16 Building Emacs on MS Windows Lars Hansen
2003-02-05 23:29 ` Juanma Barranquero
2003-02-06  5:55 ` Eli Zaretskii

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