unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Eric Lilja <mindcooler@gmail.com>, emacs-devel@gnu.org
Subject: Re: make bootstrap fails on w32/MinGW
Date: Wed, 06 Feb 2008 20:55:14 +0100	[thread overview]
Message-ID: <47AA10A2.6060909@gmail.com> (raw)
In-Reply-To: <ur6fpswcw.fsf@gnu.org>

Eli Zaretskii wrote:
>> Date: Wed, 06 Feb 2008 20:16:24 +0100
>> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
>> Cc: emacs-devel@gnu.org
>>
>> make   unidatagen-CMD
>> make[1]: Entering directory `C:/eclean/bld/emacs/nt'
>> if exist ..\admin\unidata\UnicodeData.txt \
>> 	   make -w  -C ../admin/unidata
>> make[2]: Entering directory `C:/eclean/bld/emacs/admin/unidata'
>> "../../src/oo-spd/i386/emacs.exe" -Q --multibyte -batch -f 
>> batch-byte-compile unidata-gen.el
>> Cannot open load file: encoded-kb
> 
> Please modify admin/unidata/makefile to display the value of
> EMACSLOADPATH in the rule .el.elc, then chdir there and type "make
> unidata-gen.elc".  What was the value of EMACSLOADPATH it printed?

I changed the way you suggested to Eric. I get the following:

echo "C:/eclean/bld/emacs/admin/unidata/../../lisp"
"C:/eclean/bld/emacs/admin/unidata/../../lisp"
"../../src/oo-spd/i386/emacs.exe" -Q --multibyte -batch -f 
batch-byte-compile unidata-gen.el
Cannot open load file: encoded-kb
make: *** [unidata-gen.elc] Error -1




  reply	other threads:[~2008-02-06 19:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02  1:08 make bootstrap fails on w32/MinGW Óscar Fuentes
2008-02-02  2:46 ` Jason Rumney
2008-02-02  4:24   ` Óscar Fuentes
2008-02-02 11:14   ` Eli Zaretskii
2008-02-02 16:10   ` Eli Zaretskii
2008-02-02 21:19     ` Jason Rumney
2008-02-02 22:16       ` Eli Zaretskii
2008-02-03 11:04     ` Lennart Borgman (gmail)
2008-02-03 19:42       ` Eli Zaretskii
2008-02-03 20:01         ` Eli Zaretskii
2008-02-03 23:11         ` Jason Rumney
2008-02-04 17:58           ` Lennart Borgman (gmail)
2008-02-04 18:05             ` Juanma Barranquero
2008-02-04 18:21               ` Lennart Borgman (gmail)
2008-02-04 19:28               ` Andreas Schwab
2008-02-04 20:15                 ` Juanma Barranquero
2008-02-04 20:58                   ` Stefan Monnier
2008-02-04 21:17                     ` Juanma Barranquero
2008-02-04 21:20                     ` Eli Zaretskii
2008-02-04 23:30                 ` Jason Rumney
2008-02-05  1:31                   ` Crash in titdic-convert with DOS line ends Jason Rumney
2008-02-05  4:19                     ` Kenichi Handa
2008-02-06 19:16               ` make bootstrap fails on w32/MinGW Lennart Borgman (gmail)
2008-02-06 19:44                 ` Eli Zaretskii
2008-02-06 19:55                   ` Lennart Borgman (gmail) [this message]
2008-02-06 21:41                     ` Eli Zaretskii
2008-02-06 21:59                       ` Lennart Borgman (gmail)

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=47AA10A2.6060909@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mindcooler@gmail.com \
    /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).