comparison etc/PROBLEMS @ 80127:4cab21eb920b

CX-TERM files no longer cause problems with DOS line-ends.
author Jason Rumney <jasonr@gnu.org>
date Fri, 15 Feb 2008 23:28:03 +0000
parents 6d1f448b6c77
children 28af19e6b167 f991f10f15ec
comparison
equal deleted inserted replaced
80126:6d1f448b6c77 80127:4cab21eb920b
2526 2526
2527 Some versions of mingw32 make on some versions of Windows do not seem 2527 Some versions of mingw32 make on some versions of Windows do not seem
2528 to detect the shell correctly. Try "make SHELL=cmd.exe", or if that 2528 to detect the shell correctly. Try "make SHELL=cmd.exe", or if that
2529 fails, try running make from Cygwin bash instead. 2529 fails, try running make from Cygwin bash instead.
2530 2530
2531 *** Building the MS-Windows port with Leim fails in the `leim' directory.
2532
2533 The error message might be something like this:
2534
2535 Converting d:/emacs-21.3/leim/CXTERM-DIC/4Corner.tit to quail-package...
2536 Invalid ENCODE: value in TIT dictionary
2537 NMAKE : fatal error U1077: '"../src/obj-spd/i386/emacs.exe"' : return code
2538 '0xffffffff'
2539 Stop.
2540
2541 This can happen if the Leim distribution is unpacked with a program
2542 which converts the `*.tit' files to DOS-style CR-LF text format. The
2543 `*.tit' files in the leim/CXTERM-DIC directory require Unix-style line
2544 endings to compile properly, because Emacs reads them without any code
2545 or EOL conversions.
2546
2547 The solution is to make sure the program used to unpack Leim does not
2548 change the files' line endings behind your back. The GNU FTP site has
2549 in the `/gnu/emacs/windows' directory a program called `djtarnt.exe'
2550 which can be used to unpack `.tar.gz' and `.zip' archives without
2551 mangling them.
2552
2553 *** Building `ctags' for MS-Windows with the MinGW port of GCC fails. 2531 *** Building `ctags' for MS-Windows with the MinGW port of GCC fails.
2554 2532
2555 This might happen due to a bug in the MinGW header assert.h, which 2533 This might happen due to a bug in the MinGW header assert.h, which
2556 defines the `assert' macro with a trailing semi-colon. The following 2534 defines the `assert' macro with a trailing semi-colon. The following
2557 patch to assert.h should solve this: 2535 patch to assert.h should solve this: