Skip to content
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

feed-1.3.0.0 testsuite: The IO action ‘main’ is not defined in module ‘Main’ #43

Closed
juhp opened this issue Nov 28, 2019 · 7 comments

Comments

@juhp
Copy link

juhp commented Nov 28, 2019

In the Stackage Nightly build

    Building test suite 'readme' for feed-1.3.0.0..
    [1 of 1] Compiling Main
    
    /tmp/ghc70_0/ghc_1.lpp:1:1: error:
        The IO action ‘main’ is not defined in module ‘Main’
juhp added a commit to commercialhaskell/stackage that referenced this issue Nov 28, 2019
@bergmark
Copy link
Member

bergmark commented Nov 28, 2019

@juhp Thanks. This may be an issue with the stackage build as it works otherwise. This is not a normal setup as we are compiling README.lhs with markdown-unlit, but it does contain a Main module with a main function.

test-suite readme
  ghc-options:       -Wall -pgmL markdown-unlit
  main-is:           README.lhs
[...]
  build-tool-depends:
    markdown-unlit:markdown-unlit >= 0.4 && < 0.6

@jkeuhlen
Copy link
Collaborator

jkeuhlen commented Dec 5, 2019

Is there anything else we need to do here? I'm not sure why this would fail in stackage nightly.

@felixonmars
Copy link

felixonmars commented Feb 24, 2020

I got the same problem on Arch. The problem is the file README.lhs becomes a text file in the hackage tarball, while it should be a symlink instead. It might have been generated under Windows or other environments that don't support symlinks.

Did a simple ln -sf README.md README.lhs and the build succeeded.

@jkeuhlen
Copy link
Collaborator

@felixonmars Oh that's good to know, thank you! I did generate the hackage upload on Windows. Do you know if there is a good way to get around that issue when I generate, or should I just use a unix environment instead?

@felixonmars
Copy link

@jkeuhlen I think it's easier to just generate it in a unix environment :)

@peti
Copy link

peti commented Feb 28, 2020

We have the same problem in NixOS.

@jkeuhlen
Copy link
Collaborator

I just uploaded 1.3.0.1 to hackage which was built on linux and should no longer have this issue. Thanks for the reports everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants