From: Eric Lilja <mindcooler@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Still cannot build native windows version of emacs 23.*
Date: Fri, 08 Feb 2008 16:12:27 +0100 [thread overview]
Message-ID: <fohrgr$cq5$1@ger.gmane.org> (raw)
In-Reply-To: <uir0zsd5r.fsf@gnu.org>
Eli Zaretskii wrote:
>> From: Eric Lilja <mindcooler@gmail.com>
>> Date: Thu, 07 Feb 2008 20:03:26 +0100
>>
>> Oh, I just checked out the trunk as it were a few hours before the
>> unicode merge and that builds just fine on my setup so it seems to me
>> that the cause for my build failures has to do with merge itself, not
>> because something is hosed with my setup.
>
> I had no doubt that this is the case. The problem is not in knowing
> that the unicode branch merge is the culprit, the problem is to know
> what to fix in it so it does bootstrap again, since undoing the merge
> is, quite obviously, not an option.
>
>
>
I hope I didn't send out the wrong signal because I was actually looking
forward to the merge and I was expecting there to be problems, but I'm
starting to feel quite alone now that the people who use pure mingw can
build and I cannot. Just let me know if I should run anymore "tests".
next prev parent reply other threads:[~2008-02-08 15:12 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
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 [this message]
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
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='fohrgr$cq5$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 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).