Re: [h-e-w] Building 21.1 using cygwin

[Alexander G. Burchell]

Hi,

I just tried again building Emacs using Cygwin.  It seems to work fine
so far, but I did run into the same problem you mentioned.

make[1]: Entering directory `/home/aburchell/src/emacs-21.0.104/leim'
"./../src/oo-spd/i386/emacs.exe" -batch --no-init-file --no-site-file --multibyt
e -l /home/aburchell/src/emacs-21.0.104/leim/../lisp/international/titdic-cnv \
    --eval '(batch-titdic-convert t)' \
    -dir quail ./CXTERM-DIC
Cannot open load file: /home/aburchell/src/emacs-21.0.104/leim/../lisp/internati
onal/titdic-cnv
Signal 127
make[1]: *** [quail/CCDOSPY.elc] Error 255
make[1]: Leaving directory `/home/aburchell/src/emacs-21.0.104/leim'
make: *** [all-other-dirs-gmake] Error 2

It appears that this problem is caused because Emacs 21 is built as a
non-cygwin application (gcc -mno-cywgin) so it can't recognize cygwin
paths.

I edited the file leim/makefile (not leim/makefile.nt as I had
previously stated) and changed the line

        buildlisppath=$(CURDIR)/$(dot)$(dot)/lisp

to

        buildlisppath=../lisp

The make will continue after the previous error location now and run
to completion.  The built emacs appears to work.  As the gentleman has
indicated, this may no longer work with the released version of Emacs
21.  I don't have the released version so can't check, sorry.

I don't remember installing MINGW, just Cygwin.  It may however have
escaped my recollection...

Best wishes,
-- 
Alexander G. Burchell
Wilshire Associates
address@hidden


*----*

This message is intended only for the use of the person(s) listed above 
as the intended recipient(s), and may contain information that is 
PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, 
you may not read, copy, or distribute this message or any attachment.  
If you received this communication in error, please notify us immediately 
by e-mail and then delete all copies of this message and any attachments.


In addition you should be aware that ordinary (unencrypted) e-mail sent 
through the Internet is not secure. Do not send confidential or sensitive 
information, such as social security numbers, account numbers, personal 
identification numbers and passwords, to us via ordinary (unencrypted) 
e-mail.