| Commit message (Collapse) | Author | Age |
|
|
|
| |
(cherry picked from commit a64eabfe7c5c206209fce9d00f941389ff15dd8c)
|
|
|
|
| |
(cherry picked from commit 1c0cbf8aea860d7a08948b4706846058e073f5ea)
|
|
|
|
|
|
|
| |
I found nothing like release notes. It certainly is a companion version
for nss 3.57 (parent commit). Firefox appears to be OK.
(cherry picked from commit 0cc9dd7c16ea3db534274225617c22160eca4311)
|
|
|
|
|
|
|
|
|
|
| |
Release notes seem "boring":
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.57_release_notes
My understanding is that this version will be needed in Firefox 82 released
in one month from now: https://wiki.mozilla.org/NSS:Release_Versions
(cherry picked from commit 80d90e69fef396bc7981f0dc499aabdfa33d69c8)
|
|
|
|
| |
(cherry picked from commit 2db575ecae0195a5c1d025c1180008f95b263f3c)
|
|
|
|
| |
(cherry picked from commit c01133316f7bac9d45c8afa2f4778b6cd76d1015)
|
|
|
|
|
|
|
|
|
|
| |
We expose it on the top level, but I don't think it makes sense to pull
it from a specific version of the rust tools when it is in fact version
agnostic.
This reverts a tiny portion of 912dca193aee9da77a4d429285db53729d81aa3d.
(cherry picked from commit 54b4b470c3a7149a7c459d92859a51c2e7a04cf7)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the rust toolchain 1.46.0:
https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1460-2020-08-27
Because rustc-1.46.0 enables static PIE by default for
`x86_64-unknown-linux-musl` this release will suffer from:
https://github.com/NixOS/nixpkgs/issues/94228
So this commit doesn't remove the 1.45.2 release.
This commit also specifies the right LLVM packages to use for each
rust release.
(cherry picked from commit b837bd4305144d04bdbb796507aa57691976336d)
|
|
|
|
| |
(cherry picked from commit 172f3a197e38c885bc5a183ecb12b47081d78819)
|
|
|
|
| |
(cherry picked from commit 7ea5b08cfcc5a4bdd206395f7f5922041df6178c)
|
|
|
|
|
|
|
|
| |
It's supposed to be just bugfixes. I tested building some projects with
gcc10. Also gfortran10 still builds. I don't expect issues.
This causes basically no rebuilds, as we use 9 by default.
(cherry picked from commit 51ccf2d4badea4d709f8087e3fdb3fff3956d556)
|
|
|
|
|
|
|
| |
We don't want to use Nix-built GCC's libs with prebuilt clang in this
case.
(cherry picked from commit 204dc3a88b69e64a4882852c4cf69405f7f6bc21)
|
|
|
|
|
|
|
|
| |
Follow up to the revert in e560459c5b06ce1351ae5eb8988f8ce87602058a.
This reverts commit 1936b11f63d2f58ef0c7216e53e56deb804a715e.
(cherry picked from commit 5ceea5705a1c3346d17ee44728ed442699f48863)
|
|
|
|
| |
(cherry picked from commit 1936b11f63d2f58ef0c7216e53e56deb804a715e)
|
|
|
|
| |
(cherry picked from commit cf7b63df5b9efdef4e8e1b3261d7040199f7e671)
|
|
|
|
| |
(cherry picked from commit 463db72e631e0bd4a835796324eb1981071c6ee4)
|
|
|
|
|
|
|
| |
It's not necessary to use strip -x otherwise, so let's just use it for
the JIT library.
(cherry picked from commit 41e34e76d8802feaa9c13f88a5f032c529fc74e9)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Turns out that libgccjit gets installed as a .so file, which the gcc
builder.sh didn't change: It only touched .dylib files; that means
that anything linking in libgccjit.so would receive an "Image not
found" error at load time.
With this change, we invoke `install_name_tool` on .so files too,
adjusting their dynamic linker ID, so that they too can be found.
(cherry picked from commit 175995986337e58e8ceec72d09515332fe363d3a)
|
|
|
|
|
|
|
|
| |
The default `strip` invocation tries to strip global symbols from the
library, and refuses because those are indirect symbol table
references.
(cherry picked from commit 038e86ffbb76bd54b922e68f5514102e36bec96b)
|
|
|
|
| |
(cherry picked from commit ad330434031519fd5dd7e52f32d7d8a30f36a4db)
|
|
|
|
| |
(cherry picked from commit fc0f11e3d533fadbb7d2330b3d3b50bd4eae298e)
|
|
|
|
| |
(cherry picked from commit bc9760b842abdb4aac17543a3ae8decae5e6530e)
|
|
|
|
| |
(cherry picked from commit 3f30e70d294b95acd20090b50534e7568d6b3527)
|
|
|
|
| |
(cherry picked from commit beb0339ce5dd74800fe8d57323afbb4b9dd017a0)
|
|
|
|
| |
(cherry picked from commit 48dc384a3cc28fdd8ef133df9b11ca1bd814e62e)
|
|
|
|
| |
(cherry picked from commit 2d39da2084d5286bcefcf3e45c27fb140b350b19)
|
|
|
|
|
|
| |
same as 459c60dda2406d2207d2afd90f210ffc87efde54 but for gcc10
(cherry picked from commit 0b8312660aaa34cc87bdf5e3776bcaf4c5ba3c59)
|
|
|
|
|
|
|
|
|
|
| |
This is used by mesa.drivers (still on LLVM 9) as a cache key. I've
ported that change to LLVM 11 to test it and so that it doesn't get lost
in future versions. Credit for the change goes to David McFarland.
See #93946 for details.
Co-Authored-By: David McFarland <corngood@gmail.com>
(cherry picked from commit 4a8262149139a9dee25a63a2d2c2888ede7d73dd)
|
|
|
|
|
| |
http://lists.llvm.org/pipermail/release-testers/2020-August/001321.html
(cherry picked from commit df267a4cca6814261e10e9e3cb87fb706519307d)
|
|
|
|
|
|
|
|
|
| |
http://lists.llvm.org/pipermail/release-testers/2020-July/001305.html
TODO: Enable Polly.
Co-authored-by: conferno <conferno@camfex.cz>
(cherry picked from commit 0a8334d5a0097d7235edfc12ff216cce87aa5a2c)
|
|
|
|
|
|
|
| |
This is simply the result of:
cp -r pkgs/development/compilers/llvm/10 pkgs/development/compilers/llvm/11/
(cherry picked from commit 28f2797a81e738234cdc57a688afb136f692672b)
|
|
|
|
| |
(cherry picked from commit 89567e206406672ba156ba44e23f93cc215a8223)
|
|
|
|
| |
(cherry picked from commit 92b4e00ffe12bb8381b4cb1241c8db1fd39d6549)
|
|
|
|
|
|
|
|
|
|
| |
We need to set FC so that CMake and other tools can find the fortran
compiler. Also we need to limit the hardening flags since fortify and
format don’t work with fortran.
Fixes #88449
(cherry picked from commit f42aa7e1d7ac4fb1050b73b296912fa7c7b927c2)
|
|
|
|
|
|
|
| |
Instead, we have a new `gccForLibs`, which has the appropriate
definition for e.g. avoiding `x86_32` linking problems.
(cherry picked from commit 92f96f47b05543074e61f1879769d52aa3ddfe66)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
(cherry picked from commit d0677e6d45c4acf9fdd3f09e77f7201794a45a82)
|
|
|
|
|
|
|
|
|
|
|
| |
This is needed for cross-compiling for LLVM.
After https://github.com/NixOS/nixpkgs/pull/94088, we still need some
of these, so I’ve whitelisted those that are in binutils.
/cc @DavidTruby
(cherry picked from commit b331c72f032389c7156ff1d30117f91c95bbeedb)
|
|
|
|
|
|
|
| |
This is a purely bugfix release.
See: http://lists.llvm.org/pipermail/release-testers/2020-July/001297.html
(cherry picked from commit e51d3a039929f18a8b590a62045ac5d13ad7a055)
|
|
|
|
|
|
|
|
|
| |
This disables all manpages packages depending on recommonmark. This can
be undone once recommonmark supports sphinx 3. The other
manpage-packages don't use recommonmark and don't need to be commented
out.
(cherry picked from commit c4740fcb1b939feb4491e842e5e467f9b9d91f3d)
|
|
|
|
|
|
|
|
|
| |
These llvm-prefixed utilities are not drop-in replacements for the utilities
with similar names, they are specifically for operating on LLVM IR files.
Symlinking these without the prefix causes incompatibilities with tools that
expect diff, as and others to behave normally.
(cherry picked from commit 46e5ea5af6474a7c5f841fcdb516de64b98995fe)
|
|
|
|
|
|
|
| |
Right now we add glibc to search path also -nostdinc was provided,
which breaks projects providing their own gcc.
(cherry picked from commit 96092dc93640b8ad6520a8bae6f78d62eaba0ec2)
|
|
|
|
|
|
|
| |
This fixes problems with missing symbols when using clang as library and
is most likely a result of llvm being build with RTTI enabled.
(cherry picked from commit 0f0b14258be090303c5013c2e29234040fa9766c)
|
|
|
|
|
|
|
|
|
| |
MacOS 10.15 now includes "aligned_alloc". Disagreement between the
headers and the binaries about whether aligned_alloc exists leads to
a compilation failure (see #73319 and the detailed comment in this
commit).
(cherry picked from commit 3a79681eb45df9c89d1de613114394f49582f0d6)
|
|
|
|
| |
(cherry picked from commit 60fd049b6552d73a5162109e7d8aa0839b54c398)
|
|
|
|
| |
(cherry picked from commit e492cd92a918068c50b65ea04ef062d4acc8814c)
|
|
|
|
|
|
|
| |
This will unbreak firefox and a few other packages which try to grab
some of the libcxx flags.
(cherry picked from commit 704daf7a6e4e5f26c5b0ad67ed8bd1b2090aa8ed)
|
|
|
|
|
|
|
| |
This means we can freely keep the comments up to date without the
penalty of a mass rebuild.
(cherry picked from commit 1085403acdbaa7337d6074074f69ec6698226474)
|
|
|
|
|
|
|
|
| |
The same `libsanitizer` problem as in llvm<10 and newer GCCs.
https://hydra.nixos.org/build/122902814
https://hydra.nixos.org/build/122903349
(cherry picked from commit 114f97e77e0f9bba09edf2251963495a41baeb64)
|
|
|
|
|
|
|
|
|
|
| |
https://hydra.nixos.org/build/122885657 and more.
Original upstream fix (available in llvm_10):
https://github.com/llvm/llvm-project/commit/947f9692440836dcb8d88b74b69dd379d85974ce
(cherry picked from commit 2c60e7c2d090a0b5934b50316660bd9d463789a7)
|
|
|
|
| |
(cherry picked from commit d348694fb680bc134ea893cc031439a21576a485)
|