From: Eric Lilja <mindcooler@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Still cannot build native windows version of emacs 23.*
Date: Sun, 03 Feb 2008 21:01:33 +0100 [thread overview]
Message-ID: <fo56it$eh$1@ger.gmane.org> (raw)
In-Reply-To: <uabmhvmyj.fsf@gnu.org>
Eli Zaretskii wrote:
>> From: Eric Lilja <mindcooler@gmail.com>
>> Date: Sun, 03 Feb 2008 16:52:46 +0100
>>
>> Hi, I just performed a fresh cvs checkout and tried to build a native
>> windows version, using --enable-font-backend. I'm using a cygwin bash
>> shell, with latest mingw make and cygwin's gcc in mingw mode (using
>> -mno-cygwin). I've been building cvs versions of emacs this way for a
>> few years now.
>>
>> The bootstrap fails with:
>> mingw32-make[1]: *** No rule to make target
>> `../lisp/international/charprop.el', needed by `DOC'. Stop.
>
> Are you sure there were no stale files in the tree where you
> bootstrapped?
Yes, I removed the old checkout completely.
>
> If the above does not help, please post here the full transcript of
> "configure --enable-font-backend" and "make bootstrap". This problem
> should have been solved since yesterday.
I will post again with them attached as text files. Do you have any tips
on how I should get the output into text files in the best possible way?
Just use > or something else?
>
>> Still getting alot of these warnings (for all lisp files maybe):
>> Compiling url/url-ns.elWarning: Default coding system `iso-latin-1'
>> disagrees with system codeset `cp1252' for this locale.
>> How do I avoid those in the build environment I briefly described above?
>>
>> Noticed several warnings in syntax.c relating to comparison always true
>> or false (can't remember which) due to limited range of data types or
>> something like that. You probably know what I'm talking about.
>>
>> Also noticed this:
>> In toplevel form:
>> term/mac-win.el:1146:1:Error: Invalid read syntax: "?"
>
> I see these as well. Please wait patiently until these are resolved.
> The Windows port currently needs quite a few fixes, and it will take
> time to make them. If you need a stable Emacs, I don't recommend the
> trunk right now.
>
>
>
I wish I could help. =/
next prev parent reply other threads:[~2008-02-03 20:01 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 [this message]
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
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='fo56it$eh$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.