| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
For historical reasons, callPackage has the xorg packages in scope. This
unstable building block is more versatile without the xorg hack baked in.
|
| |
|
|
|
|
|
| |
These commits all ended up on later GHCs, and are already being patched
in for ghc-8.4.3 in nixpkgs.
|
|
|
|
|
| |
Other patches are also needed for a working build, but that doesn't mean
these patches are any less necessary.
|
|
|
|
| |
Not sure why this one doesn't
|
|
|
|
| |
We really need to abstract to avoid these copy-paste errors.
|
|
|
|
| |
This is more meaningful than the GHCJS version for most tasks.
|
|
|
|
|
|
|
| |
The per-version `default.nix`es just fill in default arguments. It is
much more useful to have the `.override` from the inner `callPackage`,
for finer control. Converting the outer `callPackage` to a plain import
makes the inner one the only one, revealing its `.override`.
|
|
|
|
|
| |
There's no reason other than misleading branch names to prefer one over
another.
|
|
|
|
| |
This reverts commit 607063f61be3b19a2da054776b360d9c5b03038a.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/cc @Ericson2314
PR was https://github.com/NixOS/nixpkgs/pull/46857
This line broke MacOS cross compilation. paxctl cannot be built on
macOS. Maybe it can be fixed, but no reason to break things
unnecessarily.
Regardless, you definitely need to be more careful about backporting.
I think it’s fine to move fast and break things on master but
with release-18.09 we should be more careful. Something like more
automated testing for cross compilation would also be
helpful (hopefully even making it block).
(cherry picked from commit f9c4075873cb56464126f993d22a1a72f7cfac45)
|
| |
|
| |
|
|
|
|
|
|
| |
The compilers themselves can pull them from `bootPkgs`, where they
should always come from anyways. This enforces that, simplifies that
code, and allows use to avoid more `rec { ... }` too.
|
|
|
|
|
|
| |
This is much nicer for overlays. For example, if someone binds a new
compiler / package set, its integer-simple variation will automatically
appear.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `overrideScope` bound by `makeScope` (via special `callPackage`)
took an override in the form `super: self { … }`. But this is
dangerously close to the `self: super { … }` form used by *everything*
else, even other definitions of `overrideScope`! Since that
implementation did not even share any code either until I changed it
recently in 3cf43547f4be03d1d6eb0bbfc557e2dbc13b4095, this inconsistency
is almost certainly an oversight and not intentional.
Unfortunately, just as the inconstency is hard to debug if one just
assumes the conventional order, any sudden fix would break existing
overrides in the same hard-to-debug way. So instead of changing the
definition a new `overrideScope'` with the conventional order is added,
and old `overrideScope` deprecated with a warning saying to use
`overrideScope'` instead. That will hopefully get people to stop using
`overrideScope`, freeing our hand to change or remove it in the future.
|
|\
| |
| |
| |
| | |
Both parent commits were previously tied as the most recent ancestor to
'master' and 'release-18.09'.
|
| |
| |
| |
| | |
Additionally, the manual path manipulation becomes no longer needed.
|
| | |
|
| |
| |
| |
| |
| |
| | |
There were many reverts back and forth, but it ultimately appears that I
am the source of this mistake. I clarified the comment so as not to
confuse myself or anyone else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
1. CHOST is how one specifies the cross host platform with this
non-standard configure script. We were just getting lucky with Linux
cross.
2. install_name_tool needs the the binutils prefix.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This isn't a MUSL thing, but just needed for cross compilation to x86.
No one had tried this when all cross compilation was to linux + glibc,
hence why no one noticed this until recently.
|
| |
| |
| |
| | |
Only the regular GCC is built with a libc dependency.
|
| |
| |
| |
| | |
Want to make sure these are the same per host platform, without duplication.
|
|/
|
|
|
|
|
| |
assertions
This is needed to access attributes of derivations on platforms where
they cannot be built.
|
|
|
|
|
| |
Also switch Linux to using the official sha1 hashes for consistency.
They are gotten from https://developer.android.com/ndk/downloads/.
|
|
|
|
| |
This way it can be overridden.
|
| |
|
|
|
|
|
|
|
|
| |
A little shim derivation to get this header for Darwin, where it is
needed for cross compilation.
There's no real reason to do glibc and musl like that, but as I'm
maintaining it I suppose I can go overboard like that.
|
| |
|
|
|
|
| |
Need to get the source to get elf.h
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Intuitively, one cares mainly about the host platform: Platforms differ
in meaningful ways but compilation is morally a pure process and
probably doesn't care, or those difference are already abstracted away.
@Dezgeg also empirically confirmed that > 95% of checks are indeed of
the host platform.
Yet these attributes in the old cross infrastructure were defined to be
the build platform, for expediency. And this was never before changed.
(For native builds build and host coincide, so it isn't clear what the
intention was.)
Fixing this doesn't affect native builds, since again they coincide. It
also doesn't affect cross builds of anything in Nixpkgs, as these are no
longer used. It could affect external cross builds, but I deem that
unlikely as anyone thinking about cross would use more explicit
attributes for clarity, all the more so because the rarity of inspecting
the build platform.
|
|
|
|
|
|
|
|
|
| |
I don't know when we can/should remove them, but this at least gets
people to stop using them. The preferred alternatives also date back to
17.09 so writing forward-compatable code without extra conditions is
easy.
Beginning with these as they are the least controversial.
|
| |
|
|
|
|
|
|
|
| |
Derivations where drawing their `system` attribute from `hostPlatform`
instead of `buildPlatform`. Fix that, and add an explanatory commment.
Fixes #45993
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
options (#45840)
This, apparently, is not an official release (it's tagged, but the tarball is not
available on the official site), but this repo is the official repo mentioned on
the official site.
This fixes a bunch of very annoying bugs present in 0.99.4, e.g.
```
$ FBReader filename
```
does not crash anymore. Yay!
|
| |
|
|\
| |
| | |
dhcpcd: 6.11.5 -> 7.0.8
|
| | |
|