| Commit message (Collapse) | Author | Age |
|\ |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Initial WebAssembly/WASI cross-compilation support
|
| | |
| | |
| | |
| | |
| | | |
This isn’t really an "emulator" but it’s the closest concept we have
right now.
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is useful to make these dynamic and not bake them into gcc. This
means we don’t have to rebuild gcc to change these values. Instead, we
will pass cflags to gcc based on platform values. This was already
done hackily for android gcc (which is multi-target), but not for our
own gccs which are single target.
To accomplish this, we need to add a few things:
- add ‘arch’ to cpu
- add NIX_CFLAGS_COMPILE_BEFORE flag (goes before args)
- set -march everywhere
- set mcpu, mfpu, mmode, and mtune based on targetPlatform.gcc flags
cc-wrapper: only set -march when it is in the cpu type
Some architectures don’t have a good mapping of -march. For instance
POWER architecture doesn’t support the -march flag at all!
https://gcc.gnu.org/onlinedocs/gcc/RS_002f6000-and-PowerPC-Options.html#RS_002f6000-and-PowerPC-Options
|
|
|
|
|
|
|
|
| |
This doesn’t appear to ever have worked. binutils doesn’t seem to
support the alpha-elf target at all. It doesn’t make sense to keep
this around.
https://hydra.nixos.org/build/92403855/nixlog/1/tail
|
|
|
|
|
|
|
| |
This makes us less reliant on the systems/examples.nix. You should be
able to cross compile with just your triple:
$ nix build --arg crossSystem '{ config = "armv6l-unknown-linux-gnueabi"; }' stdenv
|
|
|
|
|
|
|
| |
ppc64le and ppc64 are different targets in the configure script. We
can’t use the same one.
TODO: canonicalize similar ones based on qemu’s configure script.
|
|
|
|
| |
Squashed to fix shell quoting, thanks @Ericson2314
|
| |
|
|\ |
|
| | |
|
| | |
|
|\| |
|
| |\
| | |
| | | |
lib: improve the implementation of the unique function
|
| | | |
|
| |\ \
| | |/
| |/| |
lib.cleanSourceFilter: Filter all .git, not just directories
|
| | |
| | |
| | |
| | |
| | | |
In the case of a worktree created with `git worktree add`, .git is
actually a file with contents pointing to the original repository.
|
|\| | |
|
| | |
| | |
| | |
| | | |
this isn’t useful any more because the ndk we use no longer supports it.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
New android ndk (18) now uses clang. We were going through the wrapper
that are provided. This lead to surprising errors when building.
Ideally we could use the llvm linker as well, but this leads to errors
as many packages don’t support the llvm linker.
|
| |\|
| | |
| | |
| | | |
Hydra nixpkgs: ?compare=1512490
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
nix-repl> map (s: s.isPyPy) [ python python3 pypy pypy3 ]
[ false false true true ]
|
|\ \ \ \
| | |_|/
| |/| | |
|
| |\ \ \
| | | | |
| | | | | |
TI MSP430 cross compiling
|
| | | | | |
|
| | | |/
| | |/| |
|
| |/ /
| | |
| | |
| | |
| | | |
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Suggested-by: Profpatsch <mail@profpatsch.de>
|
|\| |
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* origin/master: (693 commits)
buildGoModule: use go_1_12 instead of go_1_11 (#58103)
gitAndTools.lab: 0.15.2 -> 0.15.3 (#58091)
signal-desktop: 1.22.0 -> 1.23.0
added missing semicolon to documentation
terminus_font_ttf: 4.46.0 -> 4.47.0
buildGoModule: remove SSL env vars in favor of cacert in buildInputs (#58071)
dav1d: init at 0.2.1
dropbox-cli: 2018.11.28 -> 2019.02.14
atlassian-confluence: 6.14.1 -> 6.14.2
maintainers: update email for dywedir
python.pkgs.hglib: use patch to specify hg path (#57926)
chkrootkit: 0.52 -> 0.53
radare2-cutter: 1.7.2 -> 1.8.0
autorandr: 1.7 -> 1.8
pythonPackages.pyhepmc: fix build
llvm-polly/clang-polly: use latest llvm
apulse: 0.1.11.1 -> 0.1.12, cleanup
factorio: experimental 0.17.14 → 0.17.16 (#58000)
sequeler: 0.6.7 -> 0.6.8
nasc: 0.5.1 -> 0.5.2
...
|
| | |
|
|\|
| |
| |
| | |
Hydra nixpkgs: ?compare=1508887
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The explicit remove helped to uncover some hidden uses of `optionSet`
in NixOps. However it makes life harder for end-users of NixOps - it will
be impossible to deploy 19.03 systems with old NixOps, but there is no
new release of NixOps with `optionSet` fixes.
Also, "deprecation" process isn't well defined. Even that `optionSet` was
declared "deprecated" for many years, it was never announced. Hence, I
leave "deprecation" announce. Then, 3 releases after announce,
we can announce removal of this feature.
This type has to be removed, not `throw`-ed in runtime, because it makes
some perfectly fine code to fail. For example:
```
$ nix-instantiate --eval -E '(import <nixpkgs/lib>).types' --strict
trace: `types.list` is deprecated; use `types.listOf` instead
error: types.optionSet is deprecated; use types.submodule instead
(use '--show-trace' to show detailed location information)
```
|
| |
| |
| |
| |
| |
| | |
descriptions
For convenience, it's not like not having a description is deadly or something.
|
|\| |
|
| | |
|
| |\
| | |
| | | |
systems: add isCompatible handling
|
| | |
| | |
| | |
| | | |
v8 can run any wasm bytecode
|
| | | |
|
| | |
| | |
| | |
| | | |
https://en.wikipedia.org/wiki/Loris
|
|\ \ \
| | | |
| | | | |
Android and related cross fixes
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | | |
dirvish: init at 1.2.1
|
| | | |
|
|\ \ \
| | | |
| | | | |
lib/modules: Change mkAliasOptionModule to use the priority for the alias
|