summary refs log tree commit diff
path: root/pkgs/test
Commit message (Collapse)AuthorAge
...
* | tests.cc-wrapper: disable static compilation macOSJörg Thalheim2020-12-14
| | | | | | | | macOS does not support this
* | bintools-wrapper: skip dynamic linker for static binariesJörg Thalheim2020-12-14
|/ | | | | | | | Currently we set dynamic-linker unconditionally. This breaks however some static binaries i.e. rust binaries linked against musl. There is no reason we should set an elf interpreter for static binaries hence this is skipped if `-static` or `-static-pie` is either passed to our cc or ld wrapper.
* rust: Clean up target configs and test some moreJohn Ericson2020-11-28
| | | | | See the new docs for details. The difference is vis-a-vis older versions of this PR, not master.
* Merge remote-tracking branch 'upstream/master' into aj-rust-custom-targetJohn Ericson2020-11-28
|\
| * haskell: Add documentationTarball to libJoe Hermaszewski2020-11-13
| |
| * Recover the complicated situation after my bad mergeVladimír Čunát2020-10-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I made a mistake merge. Reverting it in c778945806b undid the state on master, but now I realize it crippled the git merge mechanism. As the merge contained a mix of commits from `master..staging-next` and other commits from `staging-next..staging`, it got the `staging-next` branch into a state that was difficult to recover. I reconstructed the "desired" state of staging-next tree by: - checking out the last commit of the problematic range: 4effe769e2b - `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken merge commit and its revert from that range (while keeping reapplication from 4effe769e2) - merging the last unaffected staging-next commit (803ca85c209) - fortunately no other commits have been pushed to staging-next yet - applying a diff on staging-next to get it into that state
| * Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"Vladimír Čunát2020-10-25
| | | | | | | | | | | | | | I'm sorry; I didn't notice it contained staging commits. This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
| * Merge branch 'staging-next' into stagingJan Tojnar2020-10-11
| |\
| * | installShellFiles: Add test suiteLily Ballard2020-10-08
| | |
* | | fix whitespaceAaron Janse2020-10-17
| | |
* | | remove trailing periodAaron Janse2020-10-17
| | |
* | | add `meta` to rust-sysroot testAaron Janse2020-10-17
| | |
* | | add testAaron Janse2020-10-17
| |/ |/|
* | tests.texlive: initDmitry Kalinkin2020-10-06
|/
* tests.haskell-shellFor: get compiling again(cdep)illabout2020-09-25
|
* stdenv: make -nostdinc work as intendedJörg Thalheim2020-07-23
| | | | | Right now we add glibc to search path also -nostdinc was provided, which breaks projects providing their own gcc.
* Merge pull request #84032 from teto/fix_kernel_mergeFlorian Klink2020-05-22
|\ | | | | Fix kernel configuration merge
| * kernel: fix config generationMatthieu Coudron2020-04-01
| | | | | | | | | | | | Addresses https://github.com/NixOS/nixpkgs/issues/71803: Kernel options are not merged as described, especially the "optional" aspects. The error silences legitimate warnings.
* | pkg-config-wrapper: InitJohn Ericson2020-05-16
| | | | | | | | This fixes longstanding build issues
* | cross/tests: Use `crossPkgs.runCommand` so we have `strictDeps`John Ericson2020-05-16
|/
* tests.nixos-functions: port test to pythonworldofpeace2020-02-09
|
* llvm_4: removeLuka Blaskovic2020-01-30
|
* llvm_39: removeLuka Blaskovic2020-01-30
|
* Merge remote-tracking branch 'obsidiansystems/work-on-multi-shellFor'Matthew Bauer2020-01-17
|\
| * shellFor: Refactor for consistency and crossJacquin Mininger2020-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes it work like work-on-multi from Reflex Platform. In particular, rather than making `.env` from `shellFor`, we make `.env` the primitive, and `shellFor` works by combining together the arguments of all the packages to `generic-builder` and taking the `.env` of the resulting mashup-package. There are 2 benefits of this: 1. The dependency logic is deduplicated. generic builder just concatted lists, whereas all the envs until now would sieve apart haskell and system build inputs. Now, they both decide haskell vs system the same way: according to the argument list and without reflection. Consistency is good, especially because it mean that if the build works, the shell is more likely to work. 2. Cross is handled better. For native builds, because the `ghcWithPackages` calls would shadow, we through both the regular component (lib, exe, test, bench) haskell deps and Setup.hs haskell deps in the same `ghcWithPackages` call. But for cross builds we use `buildPackages.ghcWithPackages` to get the setup deps. This ensures everything works correctly.
* | tests.cc-wrapper-{clang,libcxx}-{8,9}: add stdenv tests for LLVM 8, 9Will Dietz2019-09-19
|/
* treewide: remove redundant recvolth2019-08-28
|
* treewide: use dontUnpackworldofpeace2019-07-01
|
* treewide: remove unused variables (#63177)volth2019-06-16
| | | | | | * treewide: remove unused variables * making ofborg happy
* all-packages/test: add gcc9Stdenv, cc-wrapper-gcc9Austin Seipp2019-05-07
| | | | | | Follow up from #60860. Signed-off-by: Austin Seipp <aseipp@pobox.com>
* wasm: init cross targetMatthew Bauer2019-04-23
| | | | | | | | | Adds pkgsCross.wasm32 and pkgsCross.wasm64. Use it to build Nixpkgs with a WebAssembly toolchain. stdenv/cross: use static overlay on isWasm isWasm doesn’t make sense dynamically linked.
* cross/tests: add llvm-based testsMatthew Bauer2019-02-26
|
* llvm: support cross compilation with useLLVM flagMatthew Bauer2019-02-26
| | | | | | | | | | | | You can build (partially) with LLVM toolchain using the useLLVM flag. This works like so: nix-build -A hello --arg crossSystem '{ system = "aarch64-unknown-linux-musl"; useLLVM = true }' also don’t separate debug info in lldClang It doesn’t work currently with that setup hook. Missing build-id?
* linux: added tests for the configMatthieu Coudron2019-01-28
|
* Merge pull request #50212 from matthewbauer/host-emulatorMatthew Bauer2018-11-29
|\ | | | | Add "emulator" function to systems
| * treewide: add emulator to platformMatthew Bauer2018-11-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | You can use stdenv.hostPlatform.emulator to get an executable that runs cross-built binaries. This could be any emulator. For instance, we use QEMU to emulate Linux targets and Wine to emulate Windows targets. To work with qemu, we need to support custom targets. I’ve reworked the cross tests in pkgs/test/cross to use this functionality. Also, I’ve used talloc to cross-execute with the emulator. There appears to be a cross-execute for all waf builds. In the future, it would be nice to set this for all waf builds. Adds stdenv.hostPlatform.qemuArch attrbute to get the qemuArch for each platform.
* | Merge pull request #49290 from krebs/nix-writersJörg Thalheim2018-11-27
|\ \ | | | | | | get nix-writers into nixpkgs
| * | build-support writers: add testslassulus2018-11-27
| |/
* | pkgs/test/nixos-functions: use dummy versioningJan Malakhovski2018-11-19
| | | | | | | | | | With this OfBorg and similar tools won't report this derivation as changed every single time.
* | pkgs/test/nixos-functions: Add inline docRobert Hensing2018-11-13
| |
* | tests: Don't use pkgs.extend. OfBorg will reject it.Robert Hensing2018-11-13
| | | | | | | | The good news is that it worked as expected.
* | Add tests for pkgs.nixos and pkgs.nixosTestRobert Hensing2018-11-13
|/
* Remove openftdJan Tojnar2018-10-21
| | | | It never worked, never was added as an attribute and the website is dead.
* Merge branch 'master' into stagingVladimír Čunát2018-09-24
|\ | | | | | | Hydra: ?compare=1480463
| * tests: add variants for llvm7Will Dietz2018-09-23
| |
* | top-level/release.nix: add patchShebangs testDan Peebles2018-09-16
|/ | | This is currently failing but nobody noticed!
* pkgs/tests: Add test for LD_LIBRARY_PATHTuomas Tynkkynen2018-08-01
| | | | | | | The latest binutils upgrade silently broke this until it was fixed by https://github.com/NixOS/nixpkgs/pull/43531. So add a test.
* tests: add some cross testsMatthew Bauer2018-07-21
|
* Merge remote-tracking branch 'upstream/master' into stagingJohn Ericson2018-06-18
|\
| * tests.cc-wrapper: Fix sanitizer conditionJohn Ericson2018-06-18
| | | | | | | | | | | | | | fc9644d4c9c9d29958e9bcf1676d48d4b3026bb4 accidentally enabled the sanitizer tests for GCC on Darwin, when fixing that case was never attempted. Also inverted the condition from broken to working for clarity.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-01 22:15:56 +0000