From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-devel Digest, Vol 27, Issue 138
Date: Tue, 23 May 2006 22:13:07 +0300 [thread overview]
Message-ID: <u7j4cftbw.fsf@gnu.org> (raw)
In-Reply-To: <20060523155338.2928@henman-np.b-eng.it.to-be.co.jp>
> From: "djh" <henman@it.to-be.co.jp>
> Date: Tue, 23 May 2006 15:53:38 +0900
>
> I recently upgraded my cygwin to version 5.19 as of today (May 23, 2006)
> The emacs version was cvs update with a check-out today.
>
> I am building emacs targeted to the POSIX features of cygwin and will use cygwin's x-windows. So this is not a native Micosfot os oriented build.
>
> The make bootrap operation ran successfully for about an hour unil it aborted.
Thank you for your report.
Is this the first time you tried to build the Cygwin port, or did you
do this before? If the latter, do I understand correctly that with
previous versions of Cygwin Emacs did succeed to bootstrap
successfully?
> ./temacs --batch --load loadup bootstrap
> Loading loadup.el (source)...
> Using load-path (/cygdrive/c/emacs/cvs/emacs/lisp /cygdrive/c/emacs/cvs/emacs/lisp/emacs-lisp /cygdrive/c/emacs/cvs/emacs/lisp/language /cygdrive/c/emacs/cvs/emacs/lisp/international /cygdrive/c/emacs/cvs/emacs/lisp/textmodes)
> Cannot open load file: emacs-lisp/byte-run
> make[2]: *** [bootstrap-emacs.exe] Error 255
> make[2]: Leaving directory `/cygdrive/c/emacs/cvs/emacs/src'
> make[1]: *** [bootstrap-build] Error 2
> make[1]: Leaving directory `/cygdrive/c/emacs/cvs/emacs'
> make: *** [bootstrap] Error 2
>
> ----
>
> Here I checked out if byte-run was anywhere.
>
> $ find . -name "byte-run*" -print
> ./lisp/erc/emacs-lisp/byte-run.el
> ./lisp/erc/emacs-lisp/byte-run.elc
>
>
> So I have it but, it was not found.
How come the emacs-lisp directory wound up under lisp/erc/??? The
lisp/erc directory should include only the erc-* files, which are
parts of the erc package.
This is the reason for the problem: byte-run.* files should be in
./lisp/emacs-lisp/, not in ./lisp/erc/emacs-lisp/.
Please investigate how did it happen that the structure of your Lisp
directory tree became messed up somehow. I could think of 2 possible
reasons, depending on how did you get the CVS sources: some problem
with the CVS client or (if you moved the files in some archive and
unpacked them) with the program that unpacked the tarball. But these
are wild guesses, the real answer is on your machine.
> I am guessing that .../lisp/erc/emacs-lisp needs to be added to the load path.
> Or was byte-run supposed to be moved into an existing loadpath automatically?
Neither. It was supposed to be in a different place, which is already
on your load-path: /cygdrive/c/emacs/cvs/emacs/lisp/emacs-lisp.
next prev parent reply other threads:[~2006-05-23 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 6:53 Emacs-devel Digest, Vol 27, Issue 138 djh
2006-05-23 19:13 ` Eli Zaretskii [this message]
[not found] ` <20060524144247.3624@henman-np.b-eng.it.to-be.co.jp>
2006-05-24 18:01 ` bootrapping emacs on cygwin 5.19 with x-windows Eli Zaretskii
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=u7j4cftbw.fsf@gnu.org \
--to=eliz@gnu.org \
--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).