| | 427 | == What to look for if your build fails == |
| | 428 | |
| | 429 | This section collects typical failure cases, and what to do abouut them. |
| | 430 | |
| | 431 | === Configure can't find darcs version === |
| | 432 | |
| | 433 | When you run your configure script, it falls over with |
| | 434 | {{{ |
| | 435 | sh-2.04$ ./configure --with-gcc=c:/mingw/bin/gcc --host=i386-unknown-mingw32 |
| | 436 | configure: WARNING: If you wanted to set the --build type, don't use --host. |
| | 437 | If a cross compiler is detected then cross compile mode will be used. |
| | 438 | checking for GHC version date... -nThe system cannot find the file specified. |
| | 439 | configure: error: failed to detect version date: check that darcs is in your path |
| | 440 | }}} |
| | 441 | This error is nothing to do with `darcs`! The darcs-version test in `configure` uses `sort`, and it is picking up the Windows sort (in `c:\windows\system32`) instead of the MSYS or Cygwin sort. |
| | 442 | |
| | 443 | Solution: either hack the configure script by hand, or (better) make sure that MSYS/Cygwin are in your PATH before Windows. Since `c:\windows\system32` is, by default, in the System Environment Variable called PATH, and System Variables come first when searching for paths, you'll have to put MSYS/Cygwin bin directory in the System PATH, before `c:\windows\system32`. |
| | 444 | |
| | 445 | (Incidentally, `find` is another program that Windows has too, with different functionality to Unix.) |
