From: Eric Lilja <mindcooler@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Still cannot build native windows version of emacs 23.*
Date: Mon, 04 Feb 2008 22:14:36 +0100 [thread overview]
Message-ID: <fo7v7s$qf1$1@ger.gmane.org> (raw)
In-Reply-To: <uve54tprf.fsf@gnu.org>
Eli Zaretskii skrev:
>> Date: Mon, 04 Feb 2008 11:02:18 +0000
>> From: Jason Rumney <jasonr@gnu.org>
>> Cc: emacs-devel@gnu.org
>>
>> Eric Lilja wrote:
>>> Here's the full session log performed on fresh cvs checkout (old files
>>> removed first). Hope attaching it works (posting through gmane, it's
>>> rather big), I can host it if it doesn't work.
>> mingw32-make[2]: Entering directory `c:/blandat/editors/emacs/cvsemacs/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
>
> One possible cause is that EMACSLOADPATH is not set in the environment
> of emacs.exe. Please take a look at admin/unidata/makefile: it should
> have these two lines:
>
> export EMACSLOADPATH
> EMACSLOADPATH = $(CURDIR)/../../lisp
>
> Do you have them?
>
> If you do and it still does not work, perhaps the combination of the
> MinGW Make and the Cygwin shell causes the exported variable to cease
> to work? (But then how did it work for you before the Unicode merge?)
>
>
>
>
On line 136 I have export EMACSLOADPATH
And on line 323 I have EMACSLOADPATH = $(CURDIR)/../../lisp
Are they in their proper places?
As I said, I built emacs-23 using this environment right before the
unicode branch merge.
next prev parent reply other threads:[~2008-02-04 21:14 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 15:52 Still cannot build native windows version of emacs 23.* Eric Lilja
2008-02-03 19:50 ` Eli Zaretskii
2008-02-03 20:01 ` Eric Lilja
2008-02-04 4:06 ` Eli Zaretskii
2008-02-04 9:41 ` Eric Lilja
2008-02-04 11:02 ` Jason Rumney
2008-02-04 11:36 ` Eric Lilja
2008-02-04 11:48 ` Jason Rumney
2008-02-04 11:54 ` Eric Lilja
2008-02-04 12:13 ` Juanma Barranquero
2008-02-04 20:56 ` Eli Zaretskii
2008-02-04 20:45 ` Eli Zaretskii
2008-02-04 21:14 ` Eric Lilja [this message]
2008-02-04 21:23 ` Eli Zaretskii
2008-02-04 21:28 ` Eric Lilja
2008-02-05 4:09 ` Eli Zaretskii
2008-02-05 9:15 ` Eric Lilja
2008-02-05 20:13 ` Eli Zaretskii
2008-02-05 23:22 ` Eric Lilja
2008-02-06 4:15 ` Eli Zaretskii
2008-02-06 4:38 ` Eric Lilja
2008-02-06 19:34 ` Eli Zaretskii
2008-02-06 22:10 ` Eric Lilja
2008-02-07 4:13 ` Eli Zaretskii
2008-02-07 4:17 ` Eric Lilja
2008-02-07 19:03 ` Eric Lilja
2008-02-08 15:04 ` Eli Zaretskii
2008-02-08 15:12 ` Eric Lilja
2008-02-08 15:32 ` Eli Zaretskii
2008-02-08 21:27 ` Lennart Borgman (gmail)
2008-02-08 22:51 ` Lennart Borgman (gmail)
2008-02-09 1:51 ` Lennart Borgman (gmail)
2008-02-09 8:54 ` Eli Zaretskii
2008-02-09 9:36 ` Eli Zaretskii
2008-02-09 11:25 ` Lennart Borgman (gmail)
2008-02-09 11:44 ` Lennart Borgman (gmail)
2008-02-09 11:46 ` Eric Lilja
2008-02-09 12:02 ` Jason Rumney
2008-02-09 22:20 ` Lennart Borgman (gmail)
2008-02-09 22:28 ` Jason Rumney
2008-02-09 22:31 ` Lennart Borgman (gmail)
2008-02-09 9:33 ` Eli Zaretskii
2008-02-09 10:35 ` Eric Lilja
2008-02-09 10:50 ` Eli Zaretskii
2008-02-09 12:20 ` Eli Zaretskii
2008-02-12 11:14 ` Kenichi Handa
2008-02-04 22:12 ` Andreas Schwab
2008-02-04 22:16 ` Eric Lilja
2008-02-04 20:47 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fo7v7s$qf1$1@ger.gmane.org' \
--to=mindcooler@gmail.com \
--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 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.