From: Eli Zaretskii <eliz@gnu.org>
To: Eric Lilja <mindcooler@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Still cannot build native windows version of emacs 23.*
Date: Tue, 05 Feb 2008 06:09:17 +0200 [thread overview]
Message-ID: <uhcgot576.fsf@gnu.org> (raw)
In-Reply-To: <fo801v$tga$1@ger.gmane.org> (message from Eric Lilja on Mon, 04 Feb 2008 22:28:31 +0100)
> From: Eric Lilja <mindcooler@gmail.com>
> Date: Mon, 04 Feb 2008 22:28:31 +0100
>
> > Can you manually modify admin/unidate/makefile so that Emacs when run
> > displays the value of load-path? Then show it here.
> >
> Well, the only working emacs I have right now is GNU Emacs 22.1.50.1
> (i386-mingw-nt5.1.2600) of 2007-10-28 on MINDCOOLER. My stupid script
> proceeded to wipe out my working emacs-23 binaries thinking that the
> build went okay. Can I use this and what exactly do I need to do? Sorry
> for asking dumb questions.
No need to apologize, I didn't explain enough.
What I meant is this: modify the line in admin/unidate/makefile that
says
"../../src/oo-spd/i386/emacs.exe" -Q --multibyte -batch -f batch-byte-compile unidata-gen.el
to say this instead:
"../../src/oo-spd/i386/emacs.exe" -Q --multibyte -batch --eval "(message \"%s\" load-path)"
and then see what it displays when you run "make bootstrap".
Note that, since admin/unidate/makefile is generated by "make
bootstrap", you will either need to edit admin/unidate/makefile.w32-in
and then run nt/configure.bat to create admin/unidate/makefile, or
edit admin/unidate/makefile while "make bootstrap" runs, but before it
gets to where it executes the above line.
next prev parent reply other threads:[~2008-02-05 4:09 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
2008-02-04 21:23 ` Eli Zaretskii
2008-02-04 21:28 ` Eric Lilja
2008-02-05 4:09 ` Eli Zaretskii [this message]
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=uhcgot576.fsf@gnu.org \
--to=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 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.