* emacs snapshot tarball test build
@ 2007-03-22 6:10 djh
2007-03-23 12:43 ` Eli Zaretskii
0 siblings, 1 reply; 11+ messages in thread
From: djh @ 2007-03-22 6:10 UTC (permalink / raw)
To: emacs-devel
I was asked to try out building a snapshot tarball on cygwin and have just finished.
Platform:
gcc (GCC) 4.1.3 20070312 (prerelease)
CYGWIN_NT-5.1 1.5.24(0.156/4/2) 2007-01-31 10:57
Results:
configured and built fine.
Install did not complete successfully, but did install a workable newly built emacs.
The only problem is shown below (and maybe it is not a real problem).
--------
make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/leim'
cd lib-src; make maybe-blessmail \
MAKE='make' archlibdir='/libexec/emacs/22.0.95/i686-pc-cygwin'
make[1]: Entering directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
../src/emacs -batch --no-site-file --multibyte -l /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
make: *** [blessmail] Error 2
------
However the newly installed emacs seems to work and I am writing this letter with it and mh-e.
What comes after "blessmail" in the Make sequence I am not familiar with, but suspect that it is near the end of the install procedure if I recall correctly.
Regards,
Darel Henman
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-14 1:31 Help: build emacs in cygwin djh
@ 2007-03-22 21:41 ` Angelo Graziosi
2007-03-23 1:34 ` djh
2007-03-23 4:37 ` Richard Stallman
0 siblings, 2 replies; 11+ messages in thread
From: Angelo Graziosi @ 2007-03-22 21:41 UTC (permalink / raw)
To: djh; +Cc: emacs-devel
djh wrote:
> The only problem is shown below (and maybe it is not a real problem).
>
> --------
> make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/leim'
> cd lib-src; make maybe-blessmail \
> MAKE='make' archlibdir='/libexec/emacs/22.0.95/i686-pc-cygwin'
> make[1]: Entering directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> ../src/emacs -batch --no-site-file --multibyte -l
> /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
> Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
> make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> make: *** [blessmail] Error 2
> ------
This often happens boostraping Emacs on Cygwin.
Workaround: try to build in another nested directory.
Generally, a build with the above problem gives problems!
Cheers,
Angelo.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-22 21:41 ` emacs snapshot tarball test build Angelo Graziosi
@ 2007-03-23 1:34 ` djh
2007-03-23 9:09 ` Angelo Graziosi
2007-03-23 14:04 ` Eli Zaretskii
2007-03-23 4:37 ` Richard Stallman
1 sibling, 2 replies; 11+ messages in thread
From: djh @ 2007-03-23 1:34 UTC (permalink / raw)
To: Angelo Graziosi; +Cc: djh, emacs-devel
Thanks Angelo. But, one shouldn't have to build in a specific directory, or guess about a directory structure, and this should be an easy thing to fix.
If it is a semi-hard coded (if should a thing code be) reference or assumption in a Makefile then it should be corrected in my opinion.
It would be good to know why "make" aborted on blessmail.el. It was reported as
"Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)" below.
> djh wrote:
> > The only problem is shown below (and maybe it is not a real problem).
> > --------
> > make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/leim'
> > cd lib-src; make maybe-blessmail \
> > MAKE='make' archlibdir='/libexec/emacs/22.0.95/i686-pc-cygwin'
> > make[1]: Entering directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> > ../src/emacs -batch --no-site-file --multibyte -l
> > /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
> > Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
> > make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> > make: *** [blessmail] Error 2
> > ------
>
>
> This often happens boostraping Emacs on Cygwin.
> Workaround: try to build in another nested directory.
> Generally, a build with the above problem gives problems!
>
> Cheers,
> Angelo.
Regards,
Darel Henman
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-22 21:41 ` emacs snapshot tarball test build Angelo Graziosi
2007-03-23 1:34 ` djh
@ 2007-03-23 4:37 ` Richard Stallman
2007-03-23 13:58 ` Eli Zaretskii
1 sibling, 1 reply; 11+ messages in thread
From: Richard Stallman @ 2007-03-23 4:37 UTC (permalink / raw)
To: Angelo Graziosi; +Cc: henman, emacs-devel
This often happens boostraping Emacs on Cygwin.
Workaround: try to build in another nested directory.
Is this documented in the installation instructions?
In etc/PROBLEMS?
If not, would someone like to add that info?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-23 1:34 ` djh
@ 2007-03-23 9:09 ` Angelo Graziosi
2007-03-23 14:04 ` Eli Zaretskii
1 sibling, 0 replies; 11+ messages in thread
From: Angelo Graziosi @ 2007-03-23 9:09 UTC (permalink / raw)
To: djh; +Cc: emacs-devel
On Fri, 23 Mar 2007, djh wrote:
>
> Thanks Angelo. But, one shouldn't have to build in a specific directory, or guess about a directory structure, and this should be an easy thing to fix.
>
> If it is a semi-hard coded (if should a thing code be) reference or assumption in a Makefile then it should be corrected in my opinion.
>
> It would be good to know why "make" aborted on blessmail.el. It was reported as
> "Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)" below.
Boostrapping Emacs on Cygwin, one often has "Fatal error
(6)make[1]:..." not only at the end, when installing, with "blessmail",
but also when it starts to compile "el" files or after it has rebuilt the
final version of "emacs.exe".
Theste errors happen at random, without an evident logic.
Usually, changing the build directory (increasing the nested level) solve
the thing (same Emacs CVS source).
So correcting the Makefile left some doubts (but I can err).
Obviously, the bootstrap of the same CVS code on GNU/Linux Kubuntu does
not give any problem.
Cheers,
Angelo.
>
> > djh wrote:
> > > The only problem is shown below (and maybe it is not a real problem).
> > > --------
> > > make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/leim'
> > > cd lib-src; make maybe-blessmail \
> > > MAKE='make' archlibdir='/libexec/emacs/22.0.95/i686-pc-cygwin'
> > > make[1]: Entering directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> > > ../src/emacs -batch --no-site-file --multibyte -l
> > > /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
> > > Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
> > > make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> > > make: *** [blessmail] Error 2
> > > ------
> >
> >
> > This often happens boostraping Emacs on Cygwin.
> > Workaround: try to build in another nested directory.
> > Generally, a build with the above problem gives problems!
> >
> > Cheers,
> > Angelo.
>
> Regards,
> Darel Henman
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-22 6:10 emacs snapshot tarball test build djh
@ 2007-03-23 12:43 ` Eli Zaretskii
2007-03-28 7:32 ` djh
0 siblings, 1 reply; 11+ messages in thread
From: Eli Zaretskii @ 2007-03-23 12:43 UTC (permalink / raw)
To: djh; +Cc: emacs-devel
> From: "djh" <henman@it.to-be.co.jp>
> Date: Thu, 22 Mar 2007 15:10:36 +0900
>
> I was asked to try out building a snapshot tarball on cygwin and have just finished.
Thanks.
> Install did not complete successfully, but did install a workable newly built emacs.
>
> The only problem is shown below (and maybe it is not a real problem).
>
> --------
> make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/leim'
> cd lib-src; make maybe-blessmail \
> MAKE='make' archlibdir='/libexec/emacs/22.0.95/i686-pc-cygwin'
> make[1]: Entering directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> ../src/emacs -batch --no-site-file --multibyte -l /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
> Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
> make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> make: *** [blessmail] Error 2
To me, this looks as an evidence that the Emacs binary you built is
unreliable. So I think we should not yet add GCC 4.1.3 to the the 3
safe versions of Cygwin GCC mentioned in PROBLEMS.
Thanks for working on this.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-23 4:37 ` Richard Stallman
@ 2007-03-23 13:58 ` Eli Zaretskii
0 siblings, 0 replies; 11+ messages in thread
From: Eli Zaretskii @ 2007-03-23 13:58 UTC (permalink / raw)
To: rms; +Cc: Angelo.Graziosi, henman, emacs-devel
> From: Richard Stallman <rms@gnu.org>
> Date: Fri, 23 Mar 2007 00:37:11 -0400
> Cc: henman@it.to-be.co.jp, emacs-devel@gnu.org
>
> This often happens boostraping Emacs on Cygwin.
>
> Workaround: try to build in another nested directory.
>
> Is this documented in the installation instructions?
> In etc/PROBLEMS?
>
> If not, would someone like to add that info?
These are not workarounds that I'd recommend adding to PROBLEMS.
In general, if the problem only happens during bootstrap, and doesn't
have a good workarounds, I'd say let's ignore it. Most Emacs users
will never bootstrap.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-23 1:34 ` djh
2007-03-23 9:09 ` Angelo Graziosi
@ 2007-03-23 14:04 ` Eli Zaretskii
1 sibling, 0 replies; 11+ messages in thread
From: Eli Zaretskii @ 2007-03-23 14:04 UTC (permalink / raw)
To: djh; +Cc: Angelo.Graziosi, henman, emacs-devel
> From: "djh" <henman@it.to-be.co.jp>
> Date: Fri, 23 Mar 2007 10:34:19 +0900
> Cc: djh <henman@it.to-be.co.jp>, emacs-devel@gnu.org
>
> It would be good to know why "make" aborted on blessmail.el. It was reported as
> "Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)" below.
It's not "make" who aborted, it's Emacs. "make" just printed a
human-readable description of why Emacs died.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-23 12:43 ` Eli Zaretskii
@ 2007-03-28 7:32 ` djh
2007-03-28 20:45 ` Eli Zaretskii
0 siblings, 1 reply; 11+ messages in thread
From: djh @ 2007-03-28 7:32 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: djh, emacs-devel
> > The only problem is shown below (and maybe it is not a real problem).
> > --------
> > ../src/emacs -batch --no-site-file --multibyte -l /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
> > Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
>
> To me, this looks as an evidence that the Emacs binary you built is
> unreliable. So I think we should not yet add GCC 4.1.3 to the the 3
> safe versions of Cygwin GCC mentioned in PROBLEMS.
GCC 4.1.3 (actually gcc-core-4.1-20070312.tar.bz2 and friends) does provide for a
robust build from cvs though (or did on March 13th anyway.)
Darel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-28 7:32 ` djh
@ 2007-03-28 20:45 ` Eli Zaretskii
2007-03-29 1:54 ` djh
0 siblings, 1 reply; 11+ messages in thread
From: Eli Zaretskii @ 2007-03-28 20:45 UTC (permalink / raw)
To: djh; +Cc: henman, emacs-devel
> Cc: "djh" <henman@it.to-be.co.jp>, <emacs-devel@gnu.org>
> From: "djh" <henman@it.to-be.co.jp>
> Date: Wed, 28 Mar 2007 16:32:49 +0900
>
> > > The only problem is shown below (and maybe it is not a real problem).
> > > --------
> > > ../src/emacs -batch --no-site-file --multibyte -l /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
> > > Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
> >
> > To me, this looks as an evidence that the Emacs binary you built is
> > unreliable. So I think we should not yet add GCC 4.1.3 to the the 3
> > safe versions of Cygwin GCC mentioned in PROBLEMS.
>
> GCC 4.1.3 (actually gcc-core-4.1-20070312.tar.bz2 and friends) does provide for a
> robust build from cvs though (or did on March 13th anyway.)
How can you call it ``robust'' when it crashes while loading
blessmail?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: emacs snapshot tarball test build
2007-03-28 20:45 ` Eli Zaretskii
@ 2007-03-29 1:54 ` djh
0 siblings, 0 replies; 11+ messages in thread
From: djh @ 2007-03-29 1:54 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: djh, emacs-devel
The cvs build with 4.1.20070312 did not crash when loading blessmail, and
it hasn't yet crashed when using skk input method which gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) did frequently.
> >
> > GCC 4.1.3 (actually gcc-core-4.1-20070312.tar.bz2 and friends) does provide for a
> > robust build from cvs though (or did on March 13th anyway.)
>
> How can you call it ``robust'' when it crashes while loading
> blessmail?
So my question is why does it build cvs emacs well and not the bz2'd version.
To be accurate I should get a tarball the exact same date as the cvs version.
Darel Henman
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2007-03-29 1:54 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-22 6:10 emacs snapshot tarball test build djh
2007-03-23 12:43 ` Eli Zaretskii
2007-03-28 7:32 ` djh
2007-03-28 20:45 ` Eli Zaretskii
2007-03-29 1:54 ` djh
-- strict thread matches above, loose matches on Subject: below --
2007-03-14 1:31 Help: build emacs in cygwin djh
2007-03-22 21:41 ` emacs snapshot tarball test build Angelo Graziosi
2007-03-23 1:34 ` djh
2007-03-23 9:09 ` Angelo Graziosi
2007-03-23 14:04 ` Eli Zaretskii
2007-03-23 4:37 ` Richard Stallman
2007-03-23 13:58 ` Eli Zaretskii
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.