-
-
Notifications
You must be signed in to change notification settings - Fork 15.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
haskell gio system dependency escalation #243553
Comments
I am not aware of anything happening recently in this area.
Unfortunately, |
@maralorn Maybe this is the cabal issue we've had problems with for a while now? nixpkgs/pkgs/development/haskell-modules/configuration-ghc-9.4.x.nix Lines 164 to 192 in 405d3d3
|
Oh, wow. Good that I asked. I had been wondering what the heck was going on with those overrides. Will try out and report back. |
Okay, I think this fixes it (e.g. for
|
See also haskell/cabal#8455. The problem is that Cabal basically re-implements (It should be possible to get a fee for the argv problem by cranking |
There is the |
While working on #240387 I noticed, that I am witnessing an escalation of system dependencies for haskell-gi packages:
e.g. while trying to build
haskellPackages.webkit2gtk3-javascriptcore
:I witness errors like:
which I can iteratively (this was actually the last one) fix until I have:
in configuration-nix.nix.
Apparently I need to do similar things for
haskellPackages.gi-soup
andhaskellPackages.gi-javascriptcore
next (for reflex-dom). I also noticed, that this escalation of the number of necessary system dependency overrides had already crept into our overrides, see:nixpkgs/pkgs/development/haskell-modules/configuration-nix.nix
Lines 321 to 339 in c7ac358
What is especially unnerving about this is, how it cascades. Does nixpkgs not have any tooling to pull in transitive pkg-config dependencies? (As you can maybe tell I have no clue about this stuff.)
Now my question: Are we doing something wrong? Is this indicative of some bigger issue?
I am fine with stacking more and more overrides on this if this is our only chance, but this feels wrong.
Summoning people who touched this and/or might have some insight: @cdepillabout @sternenseemann @jtojnar @wegank @expipiplus1
The text was updated successfully, but these errors were encountered: