all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: offby1@blarg.net, emacs-devel@gnu.org
Subject: Re: CVS emacs bootstrap problem: cannot open encoded-kb
Date: Thu, 18 May 2006 06:37:23 +0300	[thread overview]
Message-ID: <u7j4k2ebw.fsf@gnu.org> (raw)
In-Reply-To: <358E19A8-1D58-4CED-9DF5-DE34A4FA002E@qwest.net> (wus@qwest.net)

> Date: Wed, 17 May 2006 18:38:30 -0700
> From: "Steven Wu" <wus@qwest.net>
> Cc: offby1@blarg.net
> 
> I knew the fix to the problem, and I applied the fix. I was
> wondering that the problem has been there since 2004, and someone
> mentioned the fix for it, but it is not in the CVS src.

It's not in the CVS because no one succeeded to explain or understand
why this problem happens in the Cygwin build, but not in any other
build, including the MS-Windows build with MinGW development tools.  I
object in principle to installing changes to problems we do not
understand, because we might be fixing the wrong code.

If you can afford the time and effort to debug this and report the
results, please do.  I can assure you that, once the problem is
understood sufficiently well, the solution will be installed in no
time.

TIA

> - lisp = $(CURDIR)
> +lisp = $(shell cygpath -m $(CURDIR))

You see, this shouldn't be needed, since subdirectories of lisp/
should be automatically on load-path--it's part of the Emacs startup
code to make this happen.  So some other factor is at work here.

  reply	other threads:[~2006-05-18  3:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18  1:38 CVS emacs bootstrap problem: cannot open encoded-kb Steven Wu
2006-05-18  3:37 ` Eli Zaretskii [this message]
     [not found]   ` <9D16FF6A-A0AE-45D3-8F75-240FB286F49C@qwest.net>
2006-05-18 18:57     ` Eli Zaretskii
2006-05-18  9:59 ` Jason Rumney
  -- strict thread matches above, loose matches on Subject: below --
2006-05-17  8:06 Steven Wu
2006-05-17 15:36 ` Eric Hanchrow
2006-05-18 10:21   ` Juanma Barranquero
2006-05-18 10:32     ` Lennart Borgman

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=u7j4k2ebw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=offby1@blarg.net \
    /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.