emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Still cannot build native windows version of emacs 23.*


From: Eric Lilja
Subject: Re: Still cannot build native windows version of emacs 23.*
Date: Wed, 06 Feb 2008 23:10:53 +0100
User-agent: Thunderbird 2.0.0.9 (Windows/20071031)

Eli Zaretskii wrote:
From: Eric Lilja <address@hidden>
Date: Wed, 06 Feb 2008 05:38:44 +0100

Hmm, what you quoted looks odd, heh.

What's odd about it?

Anyway, here are what I hope are the relevant lines from the bootstrap: mingw32-make[2]: Entering directory `c:/blandat/editors/emacs/cvsemacs/emacs/admin/unidata' "../../src/oo-spd/i386/emacs.exe" -Q --multibyte -batch --eval "(message \"%s\" load-path)" -f batch-byte-compile unidata-gen.el
Cannot open load file: encoded-kb

Strange, it looks like the setting of EMACSLOADPATH has no effect
whatsoever...  Can you see what is its value?  For example, change the
rule to

.el.elc:
        echo "$(EMACSLOADPATH)"
        $(RUNEMACS) -f batch-byte-compile $<

and then chdir to admin/unidata and type "make unidata-gen.elc" (no
need to run "make bootstrap" again).  What does it print as the value
of EMACSLOADPATH?




I changed the rule to:
.el.elc:
        echo "$(EMACSLOADPATH)"
        $(RUNEMACS) -f batch-byte-compile $<

Then I cd to admin/unidata and performed a mingw32-make unidata-gen.elc and I get:

[Please ignore a syntax error on the next line - it is intentional]
/usr/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'
/usr/bin/sh: -c: line 1: syntax error: unexpected end of file
echo "c:/blandat/editors/emacs/cvsemacs/emacs/admin/unidata/../../lisp"
c:/blandat/editors/emacs/cvsemacs/emacs/admin/unidata/../../lisp
"../../src/oo-spd/i386/emacs.exe" -Q --multibyte -batch -f batch-byte-compile unidata-gen.el
Warning: Default coding system `iso-latin-1' disagrees with
system codeset `cp1252' for this locale.
Wrote c:/blandat/editors/emacs/cvsemacs/emacs/admin/unidata/unidata-gen.elc

Hmm, no complaint about a missing encoded-kb but maybe that was expected?





reply via email to

[Prev in Thread] Current Thread [Next in Thread]