unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Phil Rooke" <phil.rooke@yax.org.uk>
Cc: emacs-devel@gnu.org
Subject: Re: [h-e-w] CVS build and subdirs.el problem
Date: Thu, 30 Jan 2003 22:46:26 -0000	[thread overview]
Message-ID: <000e01c2c8b1$6c7cf3d0$fa790251@chen> (raw)
In-Reply-To: m2ptqf36bx.fsf@nyaumo.jasonr.f2s.com

> I don't know who added the cygpath kludge to the W32 makefiles, but
> breaking the mingw32 build in order to get the broken Cygwin ports of
> make to work is a serious bug. I will remove the cygpath calls from
> the makefiles.

Thank you.  After updating my copy of the cvs sources that cygpath error
has now gone.  However, the build still fails at the same place as follows:

gmake[1]: Entering directory `D:/emacs/lisp'
echo ;; -*- no-byte-compile: t -*->subdirs.el
echo ;; In load-path, after this directory should come>> subdirs.el
echo ;; certain of its subdirectories.  Here we specify them.>> subdirs.el
echo (normal-top-level-add-to-load-path '(>> subdirs.el
d) was unexpected at this time.
gmake[1]: *** [update-subdirs-CMD] Error 255
gmake[1]: Leaving directory `D:/emacs/lisp'
gmake: *** [bootstrap-gmake] Error 2

Any other ideas?

Many thanks,

Phil

      reply	other threads:[~2003-01-30 22:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001201c2c7d4$ea29fe50$fa790251@chen>
     [not found] ` <u3cnbvdks.fsf@nasa.gov>
2003-01-29 23:05   ` [h-e-w] CVS build and subdirs.el problem Jason Rumney
2003-01-30 22:46     ` Phil Rooke [this message]

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='000e01c2c8b1$6c7cf3d0$fa790251@chen' \
    --to=phil.rooke@yax.org.uk \
    --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).