[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: |
Mon, 14 Oct 2013 08:41:25 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (windows-nt) |
Eli Zaretskii <address@hidden> writes:
I tried to fix this problem in trunk revision 114637. If you (or
someone else who would like to move to the new MinGW runtime) have
time, please re-test with v4.0 of the MinGW runtime.
Loading loadup.el (source)...
Using load-path (c:/trunk/lisp c:/trunk/lisp/emacs-lisp c:/trunk/lisp/language c
:/trunk/lisp/international c:/trunk/lisp/textmodes)
Loading emacs-lisp/byte-run...
Loading emacs-lisp/backquote...
Loading subr...
Loading version...
Specified time is not representable
cd ../lisp; make -w compile-first EMACS=/c/trunk/src/bootstrap-emacs.exe
make[2]: Entering directory `/c/trunk/lisp'
make[2]: Nothing to be done for `compile-first'.
make[2]: Leaving directory `/c/trunk/lisp'
cd ../leim && make -w leim-list.el EMACS=/c/trunk/src/bootstrap-emacs.exe
make[2]: Entering directory `/c/trunk/leim'
make[2]: Leaving directory `/c/trunk/leim'
if test "no" = "yes"; then \
rm -f emacs.exe; \
ln temacs.exe emacs.exe; \
else \
LC_ALL=C `/bin/pwd`/temacs -batch -l loadup dump || exit 1; \
test "X" = X || -zex emacs.exe; \
rm -f bootstrap-emacs.exe; \
ln emacs.exe bootstrap-emacs.exe; \
fi
Loading loadup.el (source)...
Using load-path (c:/trunk/lisp)
Loading emacs-lisp/byte-run...
Loading emacs-lisp/backquote...
Loading subr...
Loading version...
Specified time is not representable
ln: accessing `emacs.exe': No such file or directory
make[1]: *** [emacs.exe] Error 1
make[1]: Leaving directory `/c/trunk/src'
make: *** [src] Error 2
Please also try the various time-related functions, such as
decode-time, encode-time, format-time-string, and
current-time-string. This is because MinGW32 runtime 4.0 also moved
to using a 64-bit time_t type by default, which according to my
testing screws up Emacs, especially if it was built on Windows 7 and
then run on XP. So for now, I forced the MinGW32 headers to use a
32-bit time_t type. This needs to be thoroughly tested, though.
Thanks.
Well, it turns out the MinGW developers might be listening after all,
at least to some of the arguments: I'm promised that the next release
of the runtime will not call opendir/readdir from the startup code.
We shall see...
Next?
Re: windows build failure, Sean Sieger, 2013/10/12
Re: windows build failure,
Sean Sieger <=
Re: windows build failure, Sean Sieger, 2013/10/14