isPowerPC is only true on 32 bit machines;
to check the family we should use isPower here
Otherwise, e.g. `pkgsCross.powernv.buildPackages.nim` fails to eval with
`error: evaluation aborted with the following error message: 'no Nim CPU support known for powerpc64le-unknown-linux-gnu'`
* Import with callPackages
* Use buildPackages for building a cross-compiler
* Patch-out potential conflicts in nim.cfg
* Generate a configuration with toolchain detection
* Build with strictDeps enabled
- link sqlite (needed for the the stdlib sqlite module)
- update nodejs to 11.x
- use default phase order (fixes linker errors during test phase)
- substitution in ./test/async/tioselectors.nim not needed anymore
- two more tests need to be disabled
- LD=$CC workaround not needed anymore
- disable unsupported tests on aarch64
- trigger pre and post hooks
- use checkInputs instead of nativeBuildInputs
- don't override patchPhase
- remove sqlite as dependency (I don't see why it's needed)
- run checkPhase after installPhase (at least one test assumes the
standard library in ../lib relative to the nim binary)
- the broken tests pass now or don't exist anymore
- two of the tests requiring network access pass now without network access
- the tests in manyloc do not download dependencies and are passing now
* Nim 0.17.2 -> 0.18.0
* Add missing dependencies for Nim 0.18.0
Solved GC and SFML-related test failures.
Attempting to download nimble packages.
* Fix tzdata test
* Fix tworkingdir test
* Replace outdated nodejs
* Disable non-runnable tests
This PR makes a few changes to how things are done:
a) build and install "koch" - the nim make-type tool
b) use "koch" to bootstrap nim
c) build additional supporting tools such as nimble, nimgrep and nimsuggest
d) nim can use other c compilers than gcc, so instead of forcing gcc we use the one from stdenv
e) run the full test suite
We do not need the "nimble" package any longer as it is part of nim.
I've removed the trivial command in 4e72b61de.
I think `install -Dt "$out/bin"` is a better replacement anyway,
as it can be easily used to other directories than $out/bin.
/cc @ehmry who seems to maintain many packages with this usage.
(BTW, it would be better to have maintainer attribute same as github
username, as it makes pinging maintainers much easier.)
