-
Notifications
You must be signed in to change notification settings - Fork 189
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
Support cabal repl? #231
Comments
this should no longer be an issue starting with network 2.7 If I remember correctly, but certainly not with 3.0. Could you try master? |
That's good news. Please feel free to close the issue if it works for you. I don't have the time to look into it right now. |
I do not experience this issue with |
Closing this issue since it is resolved for 3.0.0.0. |
I cloned the
network
repository to try something simple in GHCi. These are the steps I took:Hmm. Perhaps something is not being built.
Okay, that was successful. Let's try GHCi again.
Progress!
Looking into
CALLCONV
... I'm not sure why it's not defined indist/build/Network/Socket/Types.hs
. But I can define it myself.Hmm. Seems like
ancilData.o
is not being linked in. Oh, let's try using the object code.Success?
No!
After researching some more, I found a trick suggested at commercialhaskell/stack#1239 (comment) to specify the object file explicitly.
Success!
After researching some more, I realize that the generated
network.buildinfo
file includes all of the host-specific configuration that extends thenetwork.cabal
.So my question is: What can be done to improve support for
cabal repl
? This brought to mind a few questions:network.cabal
?cabal repl
respect the generatednetwork.buildinfo
file?cabal repl
fornetwork
?The text was updated successfully, but these errors were encountered: