Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/xbjik2b7dbm76gjy47mrvi27iwri304z-newt-0.52.20/bin/whiptail -h` got 0 exit code
- ran `/nix/store/xbjik2b7dbm76gjy47mrvi27iwri304z-newt-0.52.20/bin/whiptail --help` got 0 exit code
- ran `/nix/store/xbjik2b7dbm76gjy47mrvi27iwri304z-newt-0.52.20/bin/whiptail -v` and found version 0.52.20
- ran `/nix/store/xbjik2b7dbm76gjy47mrvi27iwri304z-newt-0.52.20/bin/whiptail --version` and found version 0.52.20
- found 0.52.20 with grep in /nix/store/xbjik2b7dbm76gjy47mrvi27iwri304z-newt-0.52.20
- found 0.52.20 in filename of file in /nix/store/xbjik2b7dbm76gjy47mrvi27iwri304z-newt-0.52.20
cc "@viric"
Certain tools, e.g. compilers, are customarily prefixed with the name of
their target platform so that multiple builds can be used at once
without clobbering each other on the PATH. I was using identifiers named
`prefix` for this purpose, but that conflicts with the standard use of
`prefix` to mean the directory where something is installed. To avoid
conflict and confusion, I renamed those to `targetPrefix`.
Commit 093cc00cdd9d8cf31ecce5bc1dd3645c460a1b98 sets the CPP environment
variable by default, confusing the newt Makefile, which expects CPP=gcc for
computing dependencies.
I add newt, checking that it cross-builds too.
I update perf to have newt support, and now it's also finding python, whatever
that means. I've not tested if 'python' as buildInputs is enough.
svn path=/nixpkgs/trunk/; revision=31353
