From: Ben Key <BenK@FreedomScientific.com>
Subject: Re: make bootstrap fails with newest CVS sources - 2002-11-25
Date: Tue, 26 Nov 2002 17:33:21 -0500 [thread overview]
Message-ID: <762A7BB74D6AD51195EF00B0D0AA16602C3852@STPETE> (raw)
I have done some work on narrowing down what change was responsible for
breaking make bootstrap. Here are my results thus far.
After cvs update -D "3 days ago" make bootstrap works.
After cvs update -D "2 days ago" make bootstrap does not work.
This means that whatever caused make bootstrap to fail happened in the last
2 days.
Here is a list of files that were changed in the last 2 days:
etc/PROBLEMS
lisp/ChangeLog
lisp/international/code-pages.el
lisp/language/cyrillic.el
lisp/language/european.el
src/ChangeLog
src/Makefile.in
src/alloca.c
src/lisp.h
src/unexalpha.c
src/unexmacosx.c
src/w32.c
src/m/ia64.h
I am assuming that we can ignore the following:
etc/PROBLEMS
lisp/ChangeLog
src/ChangeLog
src/Makefile.in
Therefore, it is most likely that a change to one of the following is at
fault:
lisp/international/code-pages.el
lisp/language/cyrillic.el
lisp/language/european.el
src/alloca.c
src/lisp.h
src/unexalpha.c
src/unexmacosx.c
src/w32.c
src/m/ia64.h
I will let you all know if I have any more luck.
next reply other threads:[~2002-11-26 22:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 22:33 Ben Key [this message]
2002-11-26 22:58 ` make bootstrap fails with newest CVS sources - 2002-11-25 Jason Rumney
2002-11-29 15:02 ` Richard Stallman
2002-11-29 19:35 ` Jason Rumney
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 7:01 Gord Peters
2002-11-26 15:51 Ben Key
2002-11-28 7:25 ` Richard Stallman
2002-11-26 13:49 Ben Key
2002-11-26 16:21 ` Steven Tamm
2002-11-28 7:25 ` Richard Stallman
2002-11-28 7:53 ` Steven Tamm
2002-11-30 14:04 ` Richard Stallman
2002-11-25 17:29 Ben Key
2002-11-26 6:10 ` Steven Tamm
2002-11-26 7:22 ` Miles Bader
2002-11-27 7:36 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=762A7BB74D6AD51195EF00B0D0AA16602C3852@STPETE \
--to=benk@freedomscientific.com \
/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 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.