Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
stdenv/check-meta: add hint to NIXPKGS_ALLOW_* for unfree/broken/…
|
|
|
|
stdenv/native: provide patchelf on linux
|
|
system
|
|
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
|
|
I'm sorry; I didn't notice it contained staging commits.
This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing
changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
|
|
cmake: Tighten deps
|
|
|
|
|
|
stdenv: unset SDKROOT on Darwin
|
|
This hook moves systemd user service file from `lib/systemd/user` to
`share/systemd/user`. This is to allow systemd to find the user
services when installed into a user profile. The `lib/systemd/user`
path does not work since `lib` is not in `XDG_DATA_DIRS`.
|
|
stdenv/darwin: enable tapi support in cctools
|
|
dudebout/document-nix-env-multiple-output-install-bug
document nix-env bug relating to multiple output installation
|
|
|
|
The Rust `cc` crate started running `xcrun` when SDKROOT is defined:
https://github.com/alexcrichton/cc-rs/commit/a970b0ab0beecec1d9c589d2e6aa5f3ad1bd3f9b
Consequently, building crates that use newer versions of the `cc`
crate fail, because xcrun is not available in pure build environments.
|
|
mkDerivation: Introduce .inputDerivation for shell.nix build convenience
|
|
This provides consistency with the pure stdenv, which provides
patchelf this way. Native stdenv can always just manually install
patchelf on their system, but like xz, it’s unlikely to be provided in
/usr/bin/. In addition, it’s not even in the RHEL7 repos.
|
|
|
|
mkDerivation: use `Generic` as system name for Redox in cmakeFlags
|
|
This introduces the .inputDerivation attribute on all derivations
created with mkDerivation. This is another derivation that can always
build successfully and whose runtime dependencies are the build time
dependencies of the original derivation.
This allows easy building and distributing of all derivations needed to
enter a nix-shell with
nix-build shell.nix -A inputDerivation
|
|
|
|
Update gnu-config (config.sub, config.guess) to suport the Genode
platform and apply the updateAutotoolsGnuConfigScriptsHook to Genode
cross-compilation.
|
|
|
|
|
|
|
|
This was supposed to be done in 773233ca771a, but was not due to a small
mistake.
|
|
|
|
pkgsStatic: use clang for C compiler on Darwin
|
|
|
|
|
|
https://github.com/NixOS/nixpkgs/blob/496bc90c6c9b54e8200a069862e3c4fad21f9f58/doc/using/configuration.xml#L190
|
|
in nix-shell this value breaks the build because python's
packaging refuses to build timestamps that date before 1980.
|
|
mesa wayland: Fix/simplify cross
|
|
Env var will work fine.
|
|
stdenv-darwin: now with 50% less LLVM!
|
|
bintools: only add macos flags when targeting macOS
|
|
I hate the thing too even though I made it, and rather just get rid of
it. But we can't do that yet. In the meantime, this brings us more
inline with autoconf and will make it slightly easier for me to write a
pkg-config wrapper, which we need.
|
|
|
|
In my haste to unbreak eval, I screwed up and got the bit-widths,
backwards.
|
|
Otherwise eval breaks
|
|
|
|
The cross file is added in the `mkDerivation`. It isn't nice putting
build tool-specific stuff here, but our current architecture gives us
little alternative.
|
|
|
|
Fixes #85038
|
|
|
|
If the option ‘noclobber’ is set in Bash, we get an error when we
clobber an already existing env-vars. This is an okay error to ignore,
so just >| instead. Note that >| is NOT a Bashism[[1]].
Fixes #79651
[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_07_02
|
|
These files never existed, so best to not leave the reference. If
someone want to step up to maintain this, that would be fine. I don’t
have the hardware to test these out. In addition, someone tried to use
the bootstrap-tools currently built by Hydra and found that they were
broken in some unclear way.
|
|
We can’t set this for cross-compiling since we use the GNU linker.
Instead, set these flags only when targetPlatform is macOS.
Fixes #80754
Fixes #83141
|
|
Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com>
|