commercialhaskell/stack

Javier Neira

@jneira

@benjamin-macadam setting $STACK_ROOT?

Taine Zhao

@thautwarm

Can you guys save me? idris must match ==1.3.2, but the stack configuration has no specified version (latest matching version is 1.3.2)

Paolo G. Giarrusso

@Blaisorblade

@thautwarm do you need to add idris to your extra-deps? if not, I guess you'll need to provide more info :-)

Taine Zhao

@thautwarm

I hadn't done it. In fact I know I can do this, but I just feel like to avoid changing stack.yaml...

After all, I think I've already specified the version info of that dependency.

Taine Zhao

@thautwarm

However, I did now and I still want to know how to solve it without chaning stack.yaml...

Magnus Therning

@magthe

Well, idris seems to not be included in Stackage, so I believe you are pretty much forced to mention it in stack.yaml if you depend on it.

Taine Zhao

@thautwarm

Understood. I forgot the stackage-related stuffs, and I now think it makes a lot of sense!

Cary Robbins

@carymrobbins

I may have asked about this before, but is there a programmatic way for accessing the stackage API to determine resolver metadata? e.g. some sort of list-resolvers endpoint

Seems from the routes file there's not really anything like this exposed?

Coding Horribly

@codinghorribly

Hi! I'm new to Haskell, and I just used Stack to install Yesod. There were a bunch of warnings, and I'm trying to figure out if they're warning about Stack itself or Yesod (or both?). I'd be happy to try to help clean some of them up, if I can. Two examples:

x509-validation     > /tmp/stack13015/x509-validation-1.6.11/Data/X509/Validation.hs:34:1: warning: [-Wunused-imports]
x509-validation     >     The import of ‘Control.Applicative’ is redundant
x509-validation     >       except perhaps to import instances from ‘Control.Applicative’
x509-validation     >     To import instances alone, use: import Control.Applicative()
x509-validation     >    |                                   
x509-validation     > 34 | import Control.Applicative        
x509-validation     >    | ^^^^^^^^^^^^^^^^^^^^^^^^^^        
x509-validation     >

I figure that one (the one above) is validating Yesod, and found that in Yesod. But what about:

unix-time           > /tmp/stack13015/unix-time-0.4.7//usr/include/features.h:184:3: error:      
unix-time           >      warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
unix-time           >      # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
unix-time           >        ^~~~~~~                                                             
unix-time           >     |                                                                      
unix-time           > 184 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
unix-time           >     |   ^

Thanks!

Paolo G. Giarrusso

@Blaisorblade

Aren't those in the packages listed on the left column?

So, neither stack nor yesod?

And fixing the second requires C/UNIX experience

Coding Horribly

@codinghorribly

Okay, I'm pretty new to all of this, I thought x509-validation was a Stack validation library, but it's actually a separate library that Stack is leveraging?

Javier Neira

@jneira

@codinghorribly they are libraries that yesod depends on, stack should build all dependencies before even to start build yesod itself

dont worry, at beginning it could be a little it difficult :smile:

the first one is a warning and i guess it didnt stop the building (so other libraries was built after it)

Javier Neira

@jneira

the second one is a error and it stopped the build, so stack could not finish the entire process

haskell libs can use c header files and unix-time uses it extensively, i would open an issue in the github repo: https://github.com/kazu-yamamoto/unix-time/issues/new

including in the issue the log of the error and the version of you os would help maintainers

YAMAMOTO Yuji

@igrep

Why does stack (and also cabal?) have such a limitation?

Cannot use 'stack ghci' with both file targets and package targets

I got annoyed when I tried to load my package and its example code (not included in the package) at the same session of stack ghci.
I learned it can be easily avoided by typing :add path/to/example.hs after launching stack ghci.
So why doesn't stack do it automatically?

hovind

@hovind

Anyone with experience building static binaries with stack?
I'm getting a pesky

<command line>: User-specified static library could not be loaded (/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../lib/libpgport.a)
Loading static libraries is not supported in this configuration.
Try using a dynamic library instead.

when doing stack build --ghc-options='-fPIC -lpgport -lpgcommon' :aws-sync with

    ghc-options:
      - -threaded
      - -rtsopts
      - -with-rtsopts=-N
    ld-options: -static
    extra-lib-dirs:
      - ./lib/gmp-6.1.2/.libs
      - ./lib/postgres/src/interfaces/libpq
      - ./lib/postgres/src/common
      - ./lib/postgres/src/port

Kirill Zaborsky

@qrilka

@hovind the easiest way to get a proper static build probably is https://github.com/nh2/static-haskell-nix e.g. Stack uses it for its static builds

hovind

@hovind

@qrilka Thanks, will check it out!

Alexander Korablev

@kor85

@hovind are you succeeded with static libraries?

hovind

@hovind

Using static-haskell-nix I ended up getting blocked on nh2/static-haskell-nix#22, because I need libpq. There is a workaround, but my case is not that pressing, so I'll wait for upstream. nh2/static-haskell-nix#62 if you want to follow the issue which is blocked upstream by https://gitlab.haskell.org/ghc/ghc/issues/17468.

static-haskell-nix was quite plug-and-play except for upstream issues, @nh2 has been doing tremendous work.

hovind

@hovind

@kor85

Matthieu Coudron

@teto

Hi, I hit the issue "You cannot have packages and a shell-file filled at the same time in your nix-shell configuration." with stack 2.3.1 and this stack.yaml

resolver: lts-13.19
nix:
  enable: true
  shell-file: shell.nix

there is no packages defined anywhere so I wonder why the warning. There is no package.yaml either.

Kirill Zaborsky

@qrilka

@teto there is a possibility that packages are defined in your .stack/config.yaml

also verbose log of Stack could shine some light maybe (but not sure in this case)

Matthieu Coudron

@teto

@qrilka how can I get verbose logs ? I've tried several flags from stack --help without success

Paolo G. Giarrusso

@Blaisorblade

doesn’t stack take --verbose? but flag order might make a difference (I forget)

double-checking.

Paolo G. Giarrusso

@Blaisorblade

Yeah, it's --verbose

Matthieu Coudron

@teto

$ stack --stack-yaml=./stack.yaml build --verbose
2.1.3.1 x86_64 hpack-0.33.0
2020-02-15 19:21:33.643425: [debug] Loading project config file stack.yaml
2020-02-15 19:21:33.644059: [error] You cannot have packages and a shell-file filled at the same time in your nix-shell configuration.

Matthieu Coudron

@teto

I ended up running strace and stack looks into various folders including ~/.stack which indeed contains packages. verbose not very helpful there

Kirill Zaborsky

@qrilka

@teto you didn't answer about ~/.stack/config.yaml

does it have packages in it?

and what does stack.yaml contain?

Matthieu Coudron

@teto

~/.stack/config.yaml did contain packages. It works now

Kirill Zaborsky

@qrilka

great to hear that it was resolved

Robin

@robinvd

I want to staticly link a '.a' (from rust) into the binary but cant seem to get it to work. Are there any resources on this?
i have tried

    extra-libraries:
      - nameoflib
    extra-lib-dirs:
      - /locoflib/

but this only works with absolute paths, and i need a relative path as the other project is in the same repo and distributed along with it

Arian van Putten

@arianvp

Hey quick question

now with pantry; is there any semantic difference between putting things in a snapshot vs putting them in extra-deps in stack.yaml?

Loutine

@Loutine

hey guys,I'm new to haskell and I'm following the turtorial of "learn haskell" try to use stack to install ghc

1 reply

but there's something wrong when I try to "stack setup"

Exception while reading snapshot from lts-15.12:
HttpExceptionRequest Request {
  host                 = "raw.githubusercontent.com"
  port                 = 443
  secure               = True
  requestHeaders       = [("User-Agent","Haskell pantry package")]
  path                 = "/commercialhaskell/stackage-snapshots/master/lts/15/12.yaml"
  queryString          = ""
  method               = "GET"
  proxy                = Nothing
  rawBody              = False
  redirectCount        = 10
  responseTimeout      = ResponseTimeoutDefault
  requestVersion       = HTTP/1.1
}
 (InternalException (HostCannotConnect "raw.githubusercontent.com" [Network.Socket.connect: <socket: 14>: does not exist (Connection refused),Network.Socket.connect: <socket: 14>: does not exist (Connection refused)]))

Where communities thrive

People

Repo info

Activity