remove invalid argument grpc argument from override as it was removed in
8fbfbf5

Changes: https://invisible-island.net/xterm/xterm.log.html#xterm_395

Another existing bug exposed by
514b00c: the build system was
interpolating an empty SDK directory and passing `-isysroot  -g0`,
eating a compiler flag and breaking the build now that we don’t
pass a redundant `-isysroot` of our own.

Thankfully, with the new SDK pattern, we don’t need to do any of
this elaborate patching; just pointing it at the right tools from
`xcbuild` lets it figure everything out itself.

There might be a nicer way to do this, but I don’t understand qmake.

According to the top-level COPYING, ISC is the right license to use.

Changes: https://lib.openmpt.org/libopenmpt/2024/10/26/releases-0.7.11-0.6.20-0.5.34-0.4.46/

…xtension helper

The full sqlite documentation is now available in the `doc` output,
and the manual is in `man`.

…1984)

This is so satisfying to do.

Our deployment target is higher than macOS 10.15 now, and it looks
like upstream handle GSS correctly these days.

patches are from macports and debian:

- add patches to include files containing function prototypes on darwin
- fix fprintf format error -- use "%s" buffer
- check buffer for null before dereferencing
- use labs for long
- scan additional ides 4-9

Signed-off-by: Sefa Eyeoglu <[email protected]>

…0216)

…gresqlExtension helper (#344039)

Change the bootstrap on all platforms to use a version of the upstream binary
that is equal to the version that is being built, instead of a binary of one
version prior. This is necessary for the 1.82.0 release because on some
platforms (rust-lang/rust#129268) the 1.81.0 binary
can not build the 1.82.0 source. Furthermore, upstream reported that their
development process (now) usually involves building a release compiler with
itself and that "the Rust compiler must be able to build itself".

Fixes #352907

Changes: https://github.com/libgit2/libgit2/releases/tag/v1.8.4

…51258)

This one fails when tests are run with too many cores.

Closes: #353176

… true;`

Replaces / Closes #353131

A while ago `postgresql` switched to using structured attrs[1]. In the
PR it was reported that this made postgresql notably slower when
importing SQL dumps[2].

After a bit of debugging it turned out that the hardening was entirely
missing and the following combination of settings was the culprit:

    hardeningEnable = [ "pie" ];
    __structuredAttrs = true;

I.e. the combination of custom hardening settings and structured attrs.

What happened here is that internally the default and enabled hardening
flags get written into `NIX_HARDENING_ENABLE`. However, the value is a list
and the setting is not in the `env` section. This means that in the
structured-attrs case we get something like

    declare -ax NIX_HARDENING_ENABLE=([0]="bindnow" [1]="format" [2]="fortify" [3]="fortify3" [4]="pic" [5]="relro" [6]="stackprotector" [7]="strictoverflow" [8]="zerocallusedregs" [9]="pie")

i.e. an actual array rather than a string with all hardening flags being
space-separated which is what the hardening code of the cc-wrapper
expects[3].

This only happens if `hardeningEnable` or `hardeningDisable` are
explicitly set by a derivation: if none of those are set,
`NIX_HARDENING_ENABLE` won't be set by `stdenv.mkDerivation` and the
default hardening flags are configured by the setup hook of the
cc-wrapper[4].

In other words, this _only_ applies to derivations that have both custom
hardening settings _and_ `__structuredAttrs = true;`.

All values of `NIX_HARDENING_ENABLE` are well-known, so we don't have to
worry about escaping issues. Just forcing it to a string by
concatenating the list everytime solves the issue without additional
issues like eval errors when inheriting `env` from a structuredAttrs
derivation[5]. The price we're paying is a full rebuild.

[1] #294504
[2] #294504 (comment)
[3] https://github.com/NixOS/nixpkgs/blob/cf3e5d3744dc26c3498aa5dadfa0e078c632cede/pkgs/build-support/cc-wrapper/add-hardening.sh#L9
[4] https://github.com/NixOS/nixpkgs/blob/cf3e5d3744dc26c3498aa5dadfa0e078c632cede/pkgs/build-support/cc-wrapper/setup-hook.sh#L114
[5] 1e84a7f

This was changed for `qtbase` in
3be309e, but affects Qt WebEngine
as well.

The codesign binary is part of the bootstrapTools and is incompatible
with the version required by the compiler_rt build. Remove
find_program(.., codesign) from the cmake files to prevent the build
from using and then breaking due to an incompatible codesign

after
llvm/llvm-project@0b06727
clang_19 will produce errors if the function label comes after
.cfi_starproc. Vendor upstream commit
libffi/libffi@8308bed
to fix the issue

remove unused and incomplete function

file is part of the final stdenv and llvm_19 requires it for tests. add
file to the path to the early stage stdenv's for the upcoming switch to
llvm_19