| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
stdenv, haskell: bonafied GHCJS cross compilation without stdenv.cc
|
|
ghcjs-cross-without-cc
|
|
|
|
this allows correct operation with packages only having pname and version
specified, resolving issue #73737
|
|
ghcjs-cross-without-cc
|
|
js-ghcjs didn't fit in an existing categor.
|
|
|
|
This platform doesn't have a C compiler, and so relies and the changes
in the previous commit to work.
|
|
Before, we'd always use `cc = null`, and check for that. The problem is
this breaks for cross compilation to platforms that don't support a C
compiler.
It's a very subtle issue. One might think there is no problem because we
have `stdenvNoCC`, and presumably one would only build derivations that
use that. The problem is that one still wants to use tools at build-time
that are themselves built with a C compiler, and those are gotten via
"splicing". The runtime version of those deps will explode, but the
build time / `buildPackages` versions of those deps will be fine, and
splicing attempts to work this by using `builtins.tryEval` to filter out
any broken "higher priority" packages (runtime is the default and
highest priority) so that both `foo` and `foo.nativeDrv` works.
However, `tryEval` only catches certain evaluation failures (e.g.
exceptions), and not arbitrary failures (such as `cc.attr` when `cc` is
null). This means `tryEval` fails to let us use our build time deps, and
everything comes apart.
The right solution is, as usually, to get rid of splicing. Or, baring
that, to make it so `foo` never works and one has to explicitly do
`foo.*`. But that is a much larger change, and certaily one unsuitable
to be backported to stable.
Given that, we instead make an exception-throwing `cc` attribute, and
create a `hasCC` attribute for those derivations which wish to
condtionally use a C compiler: instead of doing `stdenv.cc or null ==
null` or something similar, one does `stdenv.hasCC`. This allows quering
without "tripping" the exception, while also allowing `tryEval` to work.
No platform without a C compiler is yet wired up by default. That will
be done in a following commit.
|
|
Rewrite the `stripHash` helper function with 2 differences:
* Paths starting with `--` will no longer produce an error.
* Use Bash string manipulation instead of shelling out to `grep` and
`cut`. This should be faster.
|
|
A bunch of stdenv-internal variables were deleted in
1601a7fcce389ae3f1b1b36676fd5545035566af, but these are needed in the
fixup phase, whereas the rest are just needed for the initial work
(findInputs, etc) before the user phases.
CC @matthewbauer
|
|
Unset unused variables in setup.sh
|
|
|
|
This reverts commit 71184f8e157672789602d3f28bdd3c8079800687.
|
|
There were two issues:
* builtins.getEnv was called deep into the nixpkgs tree making it hard
to discover. This is solved by moving the call into
pkgs/top-level/impure.nix
* when the config was explicitly set by the user to false, it would
still try and load the environment variable. This meant that it was
not possible to guarantee the same outcome on two different systems.
|
|
Fix handling of lists in whitelistedLicenses and blacklistedLicenses
|
|
Apparently this option trades compression time for size,
and explicitly does so without increasing resources needed in decomp.
Doesn't make tarball creation unbearable, so add it to options!
|
|
|
|
|
|
Before, we very carefully unapplied and reapplied `set -u` so the rest
of Nixpkgs could continue to not fail on undefined variables. Let's rip
off the band-aid.
|
|
Go beyond the obvious setup hooks now, with a bit of sed, with a skipped case:
- cc-wrapper's `dontlink`, because it already is handled.
Also, in nix files escaping was manually added.
EMP
|
|
A package's meta.license can either be a single license or a list. The
code to check config.whitelistedLicenses and config.blackListedLicenses
wasn't handling this, nor was the showLicense function.
|
|
setup.sh adds a bunch of variables that only it needs. To avoid
polluting environments, we should unset these as soon as we are done
with them.
|
|
Revert "setup.sh introduce isELFExec, isELFDyn"
|
|
|
|
|
|
|
|
|
|
|
|
This logic should be in the pkgs/top-level/static.nix. We don’t want
to pollute Nixpkgs with =if stdenv.static=. Also, "static" is not
descriptive. We have two types of static stdenvs, ‘makeStaticLibaries’
and ‘makeStaticBinaries’. We shouldn’t rely on a static boolean like
this.
|
|
|
|
This reverts commit e1b80a5a99a3013c6556ec2e2e73ef6ca8e8b80b.
This is broken in PIE (#68513). Best to not keep it in until something
else starts using it.
|
|
|
|
|
|
This adds enough logic to nixpkgs to support the `js-unknown-ghcjs` triple.
|
|
|
|
|
|
|
|
Postgresql plugins fixes
|
|
stdenv: add isELFExec, isELFDyn, fix wrappers
|
|
These can be used to determine whether a ELF file with ELF header is an
executable or shared library.
We can't implement it in pure bash, as bash has problems with null
bytes.
|
|
|
|
stdenv: correct cross CMAKE_SYSTEM_NAME
|
|
|
|
As described in cmake cross instructions, CMAKE_SYSTEM_NAME should be
set to "Generic" if there is no applicable OS:
https://gitlab.kitware.com/cmake/community/wikis/doc/cmake/CrossCompiling#setting-up-the-system-and-toolchain
|
|
|
|
This flag can replace the extra static parameter to packages that
don't work automatically with this adapter.
|
|
|
|
|
|
There's already 21 occurences of this and I've
expected this to exist without knowing it had no affect for a while.
|
