Re: Failures in build Emacs-CVS on Cygwin

[Angelo Graziosi]

I have asked and Cygwin suggests this:

http://cygwin.com/ml/cygwin/2006-11/msg00599.html
http://cygwin.com/ml/cygwin/2006-11/msg00600.html

I will try to understand deeply these suggestions to see how they work.

While waiting for the above answers I downloaded new CVS (which differ
very little from the previous), and now the build fails at the end of
installation, i.e. after the bootstrap!

---------------------------------------------------
...
ja-dic/CVS/Template
ja-dic/ja-dic.el
ja-dic/ja-dic.elc
unset CDPATH; \
        if [ -n "/usr/bin/gzip" ]; \
        then \
           echo "Compressing *.el ..." ; \
           (cd
/tmp/emacs/.inst/usr/local/emacs-cvs/share/emacs/22.0.91/leim; for f in
`find . -name "*.elc" -print`; do \
                /usr/bin/gzip -9n `echo $f|sed 's/.elc$/.el/'` ; \
            done) \
        else true; fi
Compressing *.el ...
chmod -R a+r /tmp/emacs/.inst/usr/local/emacs-cvs/share/emacs/22.0.91/leim
make[1]: Leaving directory `/tmp/emacs/.build/leim'
cd lib-src; make maybe-blessmail  \
          MAKE='make'
archlibdir='/tmp/emacs/.inst/usr/local/emacs-cvs/libexec/emacs/22.0.91/i686-pc-cygwin'
make[1]: Entering directory `/tmp/emacs/.build/lib-src'
../src/emacs -batch -l /tmp/emacs/lib-src/../lisp/mail/blessmail.el
Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
make[1]: Leaving directory `/tmp/emacs/.build/lib-src'
make: *** [blessmail] Error 2 
---------------------------------------------------


When all works fine, the build is completed in this way
------------------------------------------------------
...
cd lib-src; make maybe-blessmail  \
          MAKE='make'
archlibdir='/home/Angelo/Downloads/cygwin_varie/emacs-cvs/
emacs/.inst/usr/local/emacs-cvs/libexec/emacs/22.0.90/i686-pc-cygwin'
make[1]: Entering directory
`/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs
/.build/lib-src'
../src/emacs -batch -l
/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lib-s
rc/../lisp/mail/blessmail.el
Wrote
/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/.build/lib-src/blessma
il
chmod +x blessmail
Assuming /usr/spool/mail is really the mail spool directory, you should
run lib-src/blessmail
/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/.inst/
usr/local/emacs-cvs/libexec/emacs/22.0.90/i686-pc-cygwin/movemail.exe
as root, to give movemail.exe appropriate permissions.
Do that after running make install.
make[1]: Leaving directory
`/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/
.build/lib-src'

Making the binary package...

===========================================
 THE BUILD FINISHES AT 2006.11.18-15:12:52
===========================================
------------------------------------------------------




Cheers,

    Angelo.

 
On Thu, 23 Nov 2006, Eli Zaretskii wrote:

> > Date: Thu, 23 Nov 2006 01:07:40 +0100 (MET)
> > From: Angelo Graziosi <address@hidden>
> > cc: address@hidden, Joe Buehler <address@hidden>
> > 
> > On Thu, 23 Nov 2006, Eli Zaretskii wrote:
> > 
> > > > Date: Wed, 22 Nov 2006 15:49:08 +0100 (MET)
> > > > From: Angelo Graziosi <address@hidden>
> > > > cc: Eli Zaretskii <address@hidden>
> > > > 
> > > > Wrote 
> > > > /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/emacs-lisp/bytecomp.elc
> > > > Compiling 
> > > > /home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp/subr.el
> > > > Fatal error (6)/bin/sh: line 4:  2196 Aborted                 (core 
> > > > dumped) 
> > > > EMACSLOADPATH=/home/Angelo/Downloads/cygwin_varie/emacs-cvs/emacs/lisp
> > > 
> > > Does Cygwin GDB support core file (a.k.a. post-mortem) debugging?  
> > 
> > I think NO: there is not a 'core' file. The failure creates a file in lisp
> > called 'bootstrap-emacs.exe.stackdump' which contains:
> > 
> > ------------------------------------------------------------------
> > $ cat bootstrap-emacs.exe.stackdump 
> > Stack trace:
> > Frame     Function  Args
> > 0022A868  7C802532  (000006D0, 0000EA60, 000000A4, 0022A8B0)
> > 0022A988  6109745C  (00000000, 00000000, 00000000, 00000000)
> > 0022AA78  61094FDB  (00000000, 003B0023, 00230000, 00000000)
> > 0022AAD8  610954BB  (0022AAF0, 00000000, 00000094, 202EDC00)
> > 0022AB98  61095672  (00000DB8, 00000006, 202DD801, 61017A53)
> > 0022ABC8  61092AA8  (00000006, 60030000, 0022ACF8, 6109751C)
> > 0022ACB8  61017B70  (000006D0, 0000EA60, 000000A4, 0022AD00)
> > 0022ADD8  6109751C  (00000000, 0022AED8, 20C3B800, 6101BE4E)
> > 0022AEC8  61094FDB  (00000000, 61167A20, 00000400, 61167A20)
> > 0022AF28  610954BB  (0022AF40, 00000000, 00000094, 0022AF88)
> > 0022AFE8  61095672  (00000DB8, 00000006, 0022B018, 20151730)
> > 0022AFF8  61092AA8  (00000000, 20CB0000, 0022B018, 20CD3000)
> > 0022B018  20151730  (20CC0950, 211D0970, 00001AC0, 202DE004)
> > 0022B058  201521A8  (FFFDD000, 203C0003, 0022B108, 20122139)
> > 0022B0B8  20150951  (00004000, 202DD801, 0022B0F8, 200F28E5)
> > 0022B0C8  200F2E3C  (00004000, 203C001D, 0022D008, 0022B214)
> > End of stack trace (more stack frames may be present)
> > --------------------------------------------------------------
> 
> Please ask Cygwin experts how to produce human-readable backtrace
> information from this stackdump.  There must be some utility in the
> Cygwin collection to do that.
> 
> Maybe Cygwin also has a way of producing a real core file, in which
> case please try using it to investigate these crashes.
> 
> TIA
>