| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
This fixes many instances of:
```
error: use of undeclared identifier '__USE_FORTIFY_LEVEL'
```
|
| |
|
|
| |
https://github.com/NixOS/nixpkgs/issues/53925
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This "-D__nonnull\\(params\\)=" leads to a compilation failure in e.g.
the configure phase:
configure:21131: gcc -c -D__nonnull\(params\)= conftest.c >&5
<command-line>: warning: ISO C99 requires whitespace after the macro name
<command-line>: error: stray '\' in program
<command-line>: error: expected ',' or ';' before '(' token
<command-line>: error: stray '\' in program
According to the commit this isn't even needed on Linux.
I confirmed that this is an (expectable) glibc-2.34 thing by checking
that
* the issue doesn't occur with gcc 10/11 on a recent glibc-2.33 staging.
* the issue DOES occur in a docker container with Fedora rawhide (which
has glibc 2.34 and gcc 11).
|
| |
|
|
|
| |
See https://mail.gnu.org/archive/html/info-gnu/2022-02/msg00003.html for
release information.
|
| |
|
|
|
| |
The patch for 32-bit ARM was included in 4.8.0, and therefore needs to be
removed.
|
| | |
|
| |
|
|
| |
This reverts commit 4acf7fd6bc131f0d36ab2353db0a8c9fccc00855.
|
| | |
|
| |
|
|
|
| |
Add an upstream patch to fix failing tests. The patch actually affects gnulib,
which is included as a vendored dependency.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a warning to the top of each “boot” package that reads:
Note: this package is used for bootstrapping fetchurl, and thus cannot
use fetchpatch! All mutable patches (generated by GitHub or cgit) that
are needed here should be included directly in Nixpkgs as files.
This makes it clear to maintainer that they may need to treat this
package a little differently than others. Importantly, we can’t use
fetchpatch here due to using <nix/fetchurl.nix>. To avoid having stale
hashes, we need to include patches that are subject to changing
overtime (for instance, gitweb’s patches contain a version number at
the bottom).
|
| |
|
|
|
| |
When invoked without a command parameter, xargs runs echo from PATH.
This change patches xargs to use a specific Nix-built echo.
|
| | |
|
| |
|
|
| |
See https://lists.gnu.org/archive/html/info-gnu/2019-08/msg00009.html
for release information
|
| |
|
|
|
|
|
|
|
|
|
| |
HTTP -> HTTPS for :
- http://gnu.org/
- http://www.gnu.org/
- http://elpa.gnu.org/
- http://lists.gnu.org/
- http://gcc.gnu.org/
- http://ftp.gnu.org/ (except in fetchurl mirrors)
- http://bugs.gnu.org/
|
| | |
|
| | |
|
| |
|
|
|
| |
Want to get this out of here for 18.09, so it can be deprecated
thereafter.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Run-time deps aren't necessarily on the PATH, so we cannot rely on
configure finding it.
N.B. on cross `-z` support is assumed missing, which is an incorrect
assumption.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| | |
Yes, setting crossAttrs.propagatedBuildInputs is the correct value to
set to override a buildInputs from the native drv!
|
| | |
| |
| |
| | |
/cc #23152.
|
| | | |
|
| |/
|
|
|
|
|
| |
updatedb could only be run by providing the --output parameter,
because it would use a path inside the nix store as it's database.
The default for --output is now /var/cache/locatedb (the same
as in the NixOS locate service)
|
| |
|
|
|
| |
This reverts commit 55cc7700e968001c9ac79190fbcf25ed3620680a.
I hope most problems have been solved. /cc #22874.
|
| |
|
|
|
|
| |
Using the upstream patch directly. It's copied in nixpkgs, because:
- fetchpatch isn't usable at this point in bootstrapping,
- the upstream patch creates collisions in NEWS.
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 1daf2e26d221712dfbe72f9f6d2f73ef230cc43c, reversing
changes made to c0c50dfcb70d48e5b79c4ae9f1aa9d339af860b4.
It seems this is what has been causing all the reliability problems
on Hydra. I'm currently unable to find why it happens, so I'm forced
to revert the update for now. Discussion: #22874.
|
| |
|
|
| |
They won't work since glibc-2.25, and I don't like to spend more time on that.
|
| |\
| |
| |
| |
| | |
Beware that stdenv doesn't build. It seems something more will be needed
than just resolution of merge conflicts.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The strftime test fails with:
NZST-12NZDT,M9.5.0,M4.1.0/3: expected "1970-01-01 13:00:00 +1300 (NZDT)", got "1970-01-01 12:00:00 +1200 (NZST)"
The source in fact marks this test as "ahistorical", so the result on
Darwin might not be incorrect.
http://hydra.nixos.org/build/32578562/nixlog/1/raw
|
| | |
| |
| |
| |
| |
| | |
The first findutils update in six years! Changes:
https://lists.gnu.org/archive/html/info-gnu/2015-12/msg00014.html
|
| |\|
| |
| |
| | |
Many non-conflict problems weren't (fully) resolved in this commit yet.
|
| | |
| |
| |
| | |
It fails when user doesn't have permission to list all TMPDIR's parent directories.
|
| | | |
|
| |\|
| |
| |
| |
| |
| |
| |
| | |
- there were many easy merge conflicts
- cc-wrapper needed nontrivial changes
Many other problems might've been created by interaction of the branches,
but stdenv and a few other packages build fine now.
|
| | |
| |
| |
| | |
Also fix meta.platform -> meta.platforms in a few places.
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
| |
Likewise for propagatedBuildNativeInputs, etc. "buildNativeInputs"
sounds like an imperative rather than a noun phrase.
|
| |
|
|
| |
Plus a small number of obsolete packages (like old versions of qemu).
|
| |
|
|
|
| |
We only used this version on Darwin, but the regular findutils seems
to build fine.
|
| |
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=21047
|
| |
|
|
|
|
|
| |
After this, the 'bootstrap-tools' can be cross-built.
svn path=/nixpkgs/branches/stdenv-updates/; revision=20945
|
| |
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=15242
|
| |
|
|
| |
svn path=/nixpkgs/trunk/; revision=13299
|
| |
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=11685
|