unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Keiichiro Nagano" <knagano@sodan.org>
Cc: emacs-devel@gnu.org
Subject: Re: init_buffer PWD fix
Date: Mon, 22 Apr 2002 17:26:29 +0900	[thread overview]
Message-ID: <m3y9fgcf62.wl@omni-engine.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020422105409.11473Q@is>

At Mon, 22 Apr 2002 11:01:27 +0300 (IDT),
Eli Zaretskii wrote:
> Thanks for the explanation.  But I still don't see how this would cause a 
> specific failure in Emacs in some situation.  Can you describe such a 
> specific failure, complete with the commands to type outside and inside 
> Emacs, and with analysis of what happens inside init_buffer in that case?

For instance,

0. in bash shell...
1. gunzip and untar emacs-21.2.tar.gz and leim-21.2.tar.gz
2. cd to emacs-21.2/nt, and run ./configure.bat.  If you have MSVC,
   configure.bat detects it and configure to use MSVC for compiling
   Emacs.
3. type nmake.  After you have done temacs.exe and emacs.exe, You
   will get an error like this:

        "C:\home\tmp\emacs-21.2\leim/../src/obj-spd/i386/emacs.exe" -batch --no-init-file --no-site-file --multibyte -l C:/home/tmp/emacs-21.2/leim/../lisp/international/titdic-cnv  --eval "(batch-titdic-convert t)"  -dir quail ./CXTERM-DIC

Warning: arch-dependent data dir (c:/emacs/bin/) does not exist.
Warning: arch-independent data dir (c:/emacs/etc/) does not exist.
Converting c:/home/tmp/emacs-21.2/nt/CXTERM-DIC to quail-package...
Opening input file: no such file or directory, c:/home/tmp/emacs-21.2/nt/CXTERM-DIC
NMAKE : fatal error U1077: '"C:\home\tmp\emacs-21.2\leim/../src/obj-spd/i386/emacs.exe"' : return code '0xffffffff'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\VC98\bin\nmake.exe"' : return code '0x2'
Stop.

Why c:/home/tmp/emacs-21.2/nt/CXTERM-DIC?  CXTERM-DIC is at
c:/home/tmp/emacs-21.2/leim.  Because chdir ../leim is done in
makefile, and Emacs uses wrong PWD c:/home/tmp/emacs-21.2/nt to open
./CXTERM-DIC.  With the patch I post, this error will never happen.

Same problems happen quite often with Emacs Lisp products, for
example, T-gnus
(http://lists.airs.net/semi-gnus/archive/200101/msg00057.html if you
can read Japanese), whose 'Makefile's do chdir before try to invoke
Emacs to byte-compile '*.el's,

-- 
Keiichiro Nagano

  reply	other threads:[~2002-04-22  8:26 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 20:15 init_buffer PWD fix Keiichiro Nagano
2002-04-21 23:00 ` Keiichiro Nagano
2002-04-22  6:18 ` Paul Eggert
2002-04-22  7:20   ` Keiichiro Nagano
2002-04-22 11:15     ` Eli Zaretskii
2002-04-22 21:16     ` Jason Rumney
2002-04-22  7:53   ` Eli Zaretskii
2002-04-22  7:01     ` Paul Eggert
2002-04-22  8:10       ` Eli Zaretskii
2002-04-22  7:22         ` Paul Eggert
2002-04-22 11:14           ` Eli Zaretskii
2002-04-22 23:21             ` Paul Eggert
2002-04-23  6:05               ` Eli Zaretskii
2002-04-22 21:21         ` Jason Rumney
2002-04-23  5:56           ` Eli Zaretskii
2002-04-23  6:14   ` MIYASHITA Hisashi
2002-04-23 11:00     ` Eli Zaretskii
2002-04-24 17:55       ` Richard Stallman
2002-04-24 18:14         ` MIYASHITA Hisashi
2002-04-23 17:45     ` Paul Eggert
2002-04-24  6:52       ` MIYASHITA Hisashi
2002-04-24  7:13         ` Paul Eggert
2002-04-24  7:45           ` MIYASHITA Hisashi
2002-04-24 11:12             ` Eli Zaretskii
2002-04-24 10:30               ` MIYASHITA Hisashi
2002-04-24 16:03                 ` Eli Zaretskii
2002-04-24 17:13                   ` MIYASHITA Hisashi
2002-04-24 18:10                     ` Eli Zaretskii
2002-04-24 18:25                       ` MIYASHITA Hisashi
2002-04-24 19:19                     ` Paul Eggert
2002-04-24 19:41                       ` MIYASHITA Hisashi
2002-04-24 19:59                         ` MIYASHITA Hisashi
2002-04-24 20:21                         ` Paul Eggert
2002-04-24 20:41                           ` MIYASHITA Hisashi
2002-04-24 21:01                             ` Paul Eggert
2002-04-24 21:23                               ` MIYASHITA Hisashi
2002-04-24 21:35                                 ` MIYASHITA Hisashi
2002-04-25 22:52                                 ` Stefan Monnier
2002-04-25  3:42                             ` Eli Zaretskii
2002-04-24 16:47                 ` Paul Eggert
2002-04-24 17:55                   ` MIYASHITA Hisashi
2002-04-24 10:38               ` MIYASHITA Hisashi
2002-04-24 16:08                 ` Eli Zaretskii
2002-04-24 16:10                 ` Eli Zaretskii
2002-04-24  7:55           ` MIYASHITA Hisashi
2002-04-24 11:07           ` Eli Zaretskii
2002-04-24 11:05         ` Eli Zaretskii
2002-04-24 10:31           ` MIYASHITA Hisashi
2002-04-24 16:05             ` Eli Zaretskii
2002-04-22  7:03 ` Eli Zaretskii
2002-04-22  6:49   ` Keiichiro Nagano
2002-04-22  8:01     ` Eli Zaretskii
2002-04-22  8:26       ` Keiichiro Nagano [this message]
2002-04-22 11:19         ` 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=m3y9fgcf62.wl@omni-engine.com \
    --to=knagano@sodan.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).