> Do you want to try to apply the GHC patch mentioned in the issue and open a
> PR if it successfully resolves your issue?
What I have already done is ask here for a proper resolution.
Last call for merge requests for GHC 8.0.2 • /r/haskell
According to ezyang the patch is probably not the
On Thu, Sep 1, 2016 at 11:37 AM, Pierre Radermecker
wrote:
> Is there something I can do ?
Do you want to try to apply the GHC patch mentioned in the issue and open a
PR if it successfully resolves your issue?
___
nix-dev
> boot.kernelPackages = pkgs.linuxPackages_latest;
As a further note, I have tried to update the kernel to latest within a
virtualbox guest but it fails (xorg does not boot up). So I have had a go with
linuxPackages_4_6 and it did work and fix the problem.
On the other hand, I am also using
On Thu, Sep 1, 2016 at 10:03 AM, Eelco Dolstra
wrote:
> The fix would be to build GHC with --disable-large-address-space or
> apply patch https://ghc.haskell.org/trac/ghc/ticket/12495.
>
There's an issue mentionning this:
It is common practice when developing against relatively recent features
to handle ENOSYS/EINVAL/etc. in *application* code. It's completely
proper that the library exports it anyway.
Kevin Cox writes:
> On Sep 1, 2016 10:03, "Eelco Dolstra"
On Sep 1, 2016 10:03, "Eelco Dolstra" wrote:
>
> Hi,
>
> On 09/01/2016 10:09 AM, Kevin Cox wrote:
>
> > Sounds more like we need glibc to support the kernel we are using. GHC
is
> > behaving fine and probably not the only program to have this problem.
>
> Glibc
Hi,
On 09/01/2016 10:09 AM, Kevin Cox wrote:
> Sounds more like we need glibc to support the kernel we are using. GHC is
> behaving fine and probably not the only program to have this problem.
Glibc supports our kernel just fine - it just makes available some features that
our kernel doesn't
On Sep 1, 2016 09:04, "Eelco Dolstra" wrote:
>
>
> I guess we need to stop GHC from using it? We can't really have GHC not
working
> on our default kernel :-)
>
Sounds more like we need glibc to support the kernel we are using. GHC is
behaving fine and probably not
Hi,
On 09/01/2016 12:58 AM, Thomas Tuegel wrote:
> If you're a Haskell user and run NixOS unstable or newer, by now you
> have probably seen the message:
>
> "unable to decommit memory: Invalid argument"
>
> coming from GHC-built programs. The short version is, you need the
> latest Linux
Thomas,
thank you for explaining this! I saw this message but had no time to debug
it yet. Cheers!
2016-08-31 23:58 GMT+01:00 Thomas Tuegel :
> Hello nix-dev!
>
> If you're a Haskell user and run NixOS unstable or newer, by now you
> have probably seen the message:
>
>
Hello nix-dev!
If you're a Haskell user and run NixOS unstable or newer, by now you
have probably seen the message:
"unable to decommit memory: Invalid argument"
coming from GHC-built programs. The short version is, you need the
latest Linux kernel; try with
boot.kernelPackages =
11 matches
Mail list logo