[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: windows build failure
From: |
Sean Sieger |
Subject: |
Re: windows build failure |
Date: |
Fri, 20 Sep 2013 12:34:28 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (windows-nt) |
Eli Zaretskii <address@hidden> writes:
> From: Sean Sieger <address@hidden>
> Date: Fri, 20 Sep 2013 10:24:46 -0400
>
> Btw, the switch to 64-bit time_t (or, more accurately, the
> corresponding switch to 64-bit time functions) is one of the few
> changes in MinGW 4.x that cause binary incompatibility with previous
> versions. So my recommendation not to use MinGW 4.x, especially if
> you are running Emacs on XP, still stands.
>
> Well, I'll see how it goes. I'm gonna try unpacking gtk, libxml2 and
> gnutls over it next. I stand forewarned.
Does the below work as expected?
emacs -Q c*.c
If you do this from the src directory, you should end up with visiting
the 14 C files that match the wildcard in the Emacs's src directory.
What do you get in Emacs linked with the new MinGW runtime?
Wait, wait, wait ...
MinGW-Shell:
address@hidden /c/trunk/src/
$ emacs -Q c*.c
... I get the correct result.
Command Prompt:
c:\trunk\src>emacs -Q c*.c
... nope, visits the non-existent, `c*.c'.
- Re: windows build failure, (continued)
- Re: windows build failure, Sean Sieger, 2013/09/18
- Re: windows build failure, Sean Sieger, 2013/09/19
- Re: windows build failure, Eli Zaretskii, 2013/09/19
- Re: windows build failure, Sean Sieger, 2013/09/19
- Re: windows build failure, Eli Zaretskii, 2013/09/19
- Re: windows build failure, Sean Sieger, 2013/09/19
- Re: windows build failure, Eli Zaretskii, 2013/09/20
- Re: windows build failure, Sean Sieger, 2013/09/20
- Re: windows build failure, Eli Zaretskii, 2013/09/20
- Re: windows build failure, Sean Sieger, 2013/09/20
- Re: windows build failure,
Sean Sieger <=
- Re: windows build failure, Eli Zaretskii, 2013/09/20