From: "djh" <henman@it.to-be.co.jp>
To: "Angelo Graziosi" <Angelo.Graziosi@roma1.infn.it>
Cc: djh <henman@it.to-be.co.jp>, emacs-devel@gnu.org
Subject: Re: emacs snapshot tarball test build
Date: Fri, 23 Mar 2007 10:34:19 +0900 [thread overview]
Message-ID: <20070323103419.2652@henman-np.b-eng.it.to-be.co.jp> (raw)
In-Reply-To: Your message of Thu, 22 Mar 2007 22:41:22 +0100 (MET) <Pine.OSF.4.21.0703222231360.16628-100000@ax0rm1.roma1.infn.it>
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
next prev parent reply other threads:[~2007-03-23 1:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 11:27 Help: build emacs in cygwin (fwd) Angelo Graziosi
2007-03-09 15:24 ` Eli Zaretskii
2007-03-13 13:10 ` Help: build emacs in cygwin Angelo Graziosi
2007-03-13 18:23 ` Harald Maier
2007-03-14 0:52 ` Angelo Graziosi
2007-03-14 1:31 ` djh
2007-03-14 7:41 ` Jason Rumney
2007-03-22 21:41 ` emacs snapshot tarball test build Angelo Graziosi
2007-03-23 1:34 ` djh [this message]
2007-03-23 9:09 ` Angelo Graziosi
2007-03-23 14:04 ` Eli Zaretskii
2007-04-04 11:32 ` Pretest 22.0.97 Angelo Graziosi
2007-04-13 11:47 ` Build failure on Cygwin Angelo Graziosi
2007-05-14 20:56 ` merging Unicode branch and availability of Windows binaries Angelo Graziosi
2007-05-14 21:13 ` Drew Adams
2007-03-23 4:37 ` emacs snapshot tarball test build Richard Stallman
2007-03-23 13:58 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2007-03-22 6:10 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070323103419.2652@henman-np.b-eng.it.to-be.co.jp \
--to=henman@it.to-be.co.jp \
--cc=Angelo.Graziosi@roma1.infn.it \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).