| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
| |
Second attempt of 8929989614589ee3acd070a6409b2b9700c92d65; see that
commit for details.
This reverts commit 0bc275e63423456d6deb650e146120c39c1e0723.
|
|
|
|
|
|
|
| |
This is a stdenv-rebuild, and should not be merged
into master
This reverts commit 8929989614589ee3acd070a6409b2b9700c92d65.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `platform` field is pointless nesting: it's just stuff that happens
to be defined together, and that should be an implementation detail.
This instead makes `linux-kernel` and `gcc` top level fields in platform
configs. They join `rustc` there [all are optional], which was put there
and not in `platform` in anticipation of a change like this.
`linux-kernel.arch` in particular also becomes `linuxArch`, to match the
other `*Arch`es.
The next step after is this to combine the *specific* machines from
`lib.systems.platforms` with `lib.systems.examples`, keeping just the
"multiplatform" ones for defaulting.
|
| |
|
| |
|
|
|
|
| |
Tested pkgsCross.armv7l-hf-multiplatform.klibc
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
treewide replacement of
stdenv.mkDerivation rec {
name = "*-${version}";
version = "*";
to pname
|
|
|
|
|
| |
Want to get this out of here for 18.09, so it can be deprecated
thereafter.
|
|
|
|
|
|
|
|
|
| |
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`.
|
| |
|
|\ |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
Build-tested on x86_64 Linux and on Darwin.
|
|\| |
|
| |
| |
| |
| |
| | |
klibc was the only user of kernelHeaders; it should use the Linux API
headers, however.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The following parameters are now available:
* hardeningDisable
To disable specific hardening flags
* hardeningEnable
To enable specific hardening flags
Only the cc-wrapper supports this right now, but these may be reused by
other wrappers, builders or setup hooks.
cc-wrapper supports the following flags:
* fortify
* stackprotector
* pie (disabled by default)
* pic
* strictoverflow
* format
* relro
* bindnow
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In most cases, this just meant changing kernelDev (now removed from
linuxPackagesFor) to kernel.dev. Some packages needed more work (though
whether that was because of my changes or because they were already
broken, I'm not sure). Specifics:
* psmouse-alps builds on 3.4 but not 3.10, as noted in the comments that
were already there
* blcr builds on 3.4 but not 3.10, as noted in comments that were
already there
* open-iscsi, ati-drivers, wis-go7007, and openafsClient don't build on
3.4 or 3.10 on this branch or on master, so they're marked broken
* A version-specific kernelHeaders package was added
The following packages were removed:
* atheros/madwifi is superceded by official ath*k modules
* aufs is no longer used by any of our kernels
* broadcom-sta v6 (which was already packaged) replaces broadcom-sta
* exmap has not been updated since 2011 and doesn't build
* iscis-target has not been updated since 2010 and doesn't build
* iwlwifi is part of mainline now and doesn't build
* nivida-x11-legacy-96 hasn't been updated since 2008 and doesn't build
Everything not specifically mentioned above builds successfully on 3.10.
I haven't yet tested on 3.4, but will before opening a pull request.
Signed-off-by: Shea Levy <shea@shealevy.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First, pass in `self' again so that overriding works properly (thanks
for pointing that out, @edolstra)
Second, instead of having linuxPackages*.kernel mean something different
inside the set and out, add a new attribute linuxPackages*.kernelDev,
which for the generic kernel is simply linuxPackages*.kernel but for the
manual-config kernel is the `dev' output (which has the build tree,
source tree, etc.)
The second change required trivial modifications in a bunch of
expressions, I verified that all of the linuxPackages* sets defined in
all-packages.nix have the same drv paths before and after the change.
Signed-off-by: Shea Levy <shea@shealevy.com>
|
|
|
|
|
| |
Likewise for propagatedBuildNativeInputs, etc. "buildNativeInputs"
sounds like an imperative rather than a noun phrase.
|
|
|
|
|
|
| |
P.S. the only reason we need klibc is because of the "nfsmount"
program in the initrd. But I'm pretty sure we can use Busybox's mount
command there.
|
|
|
|
|
|
| |
can be distinguished in nix-env -qa output.
svn path=/nixpkgs/trunk/; revision=32352
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=30009
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=30008
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=23705
|
|
|
|
|
|
| |
It fails building, but at least does not annoy that much.
svn path=/nixpkgs/branches/stdenv-updates/; revision=23640
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=22848
|
|\
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=22254
|
| |
| |
| |
| | |
svn path=/nixpkgs/trunk/; revision=22083
|
|/
|
|
|
|
|
| |
After this, the 'bootstrap-tools' can be cross-built.
svn path=/nixpkgs/branches/stdenv-updates/; revision=20945
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=19067
|
|
|
|
|
|
|
|
|
|
|
|
| |
This comes from:
svn diff ^/nixpkgs/trunk/@18255 ^/nixpkgs/branches/stdenv-updates/ > diff
patch -p0 < diff
and then adding into svn all files new from the patch.
trunk@18255 comes from the last time I updated stdenv-updates from trunk.
svn path=/nixpkgs/stdenv-updates2/; revision=18272
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=16020
|
|
|
|
|
|
|
|
|
|
| |
* klibc: build against the regular kernel headers instead of depending
on a kernel build. This way we don't have to rebuild klibc every
time the kernel changes.
* splashutils 1.3: compile properly with a klibc that uses unpatched
kernel headers.
svn path=/nixpkgs/trunk/; revision=13900
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=13172
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=12563
|
|
|
|
|
|
|
|
| |
library.
* Removed devicemapperStatic, e2fsprogsDiet, lvm2Static since they're
redundant (it's what you get when you use pkgsDiet/pkgsStatic).
svn path=/nixpkgs/trunk/; revision=12554
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=9202
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=8295
|
|
|
|
|
|
| |
* Latest klibc.
svn path=/nixpkgs/trunk/; revision=7871
|
|
|
|
|
|
|
| |
from the fbsplash kernel patch. So use the actual patched kernel as
an input to klibc, instead of Glibc's kernel headers.
svn path=/nixpkgs/trunk/; revision=7138
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=7133
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=7126
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=4623
|
|
svn path=/nixpkgs/trunk/; revision=3723
|