all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Subject: Building Emacs from CVS on windows nt failed
Date: Sun, 17 Oct 2004 15:42:52 +0200	[thread overview]
Message-ID: <004d01c4b44f$3cf4d1b0$0200a8c0@sedrcw11488> (raw)

I took some time to download the CVS version and started building it. It
fails in make boostrap with the following:

Wrote c:/emacscvs/emacs/lisp/finder-inf.el
touch cus-load.el
Can't touch cus-load.el - No such file or directory
make[1]: *** [cus-load.el] Error 1
make[1]: Leaving directory `/c/emacscvs/emacs/lisp'
make: *** [bootstrap-gmake] Error 2

I guess it is not very important in this case (cus-load.el seems to be
missing, can't find it in WebCVS either), but I am using current MinGW and
MSYS.

I have however another point about this. When things fail on ms windows you
immediately starting wondering whether the build process for ms windows is
updated or not. I am very far from beeing a compiler expert and posix
expert, but I wonder if it would not be better merge the building processes
so that windows nt was built the same way as the unix or GNU/Linux builds? I
have got the impression that several people would like something like that
to happen.

I wonder if MSYS is enough for that? Is the make that comes with MSYS GNU
make? Is the MSYS shell good enough? Are the any problems with building with
MSVC? Maybe the NMakeFile is built by the MSVC?

I can understand that a separate build process for ms windows was once
created. My question is whether it is still useful or something that takes
extra time for many people.

- Lennart

             reply	other threads:[~2004-10-17 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17 13:42 Lennart Borgman [this message]
2004-10-17 16:17 ` Building Emacs from CVS on windows nt failed Jason Rumney
2004-10-17 18:11 ` Lennart Borgman
2004-10-17 18:49   ` Lennart Borgman
2004-10-17 18:49   ` Stefan Monnier

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='004d01c4b44f$3cf4d1b0$0200a8c0@sedrcw11488' \
    --to=lennart.borgman.073@student.lu.se \
    /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.