2 Configuring AutogenModules-0.1...
4 [autogen-not-exposed] An 'autogen-module' is neither on 'exposed-modules' nor 'other-modules'.
6 [autogen-other-modules] On executable 'Exe' an 'autogen-module' is not on 'other-modules'
8 [autogen-other-modules] On test suite 'Test' an 'autogen-module' is not on 'other-modules'
10 [autogen-other-modules] On benchmark 'Bench' an 'autogen-module' is not on 'other-modules'
12 Distribution quality errors:
13 [autogen-not-exposed] An 'autogen-module' is neither on 'exposed-modules' nor 'other-modules'.
14 [autogen-other-modules] On executable 'Exe' an 'autogen-module' is not on 'other-modules'
15 [autogen-other-modules] On test suite 'Test' an 'autogen-module' is not on 'other-modules'
16 [autogen-other-modules] On benchmark 'Bench' an 'autogen-module' is not on 'other-modules'
17 [no-autogen-paths] Packages using 'cabal-version: 2.0' and the autogenerated module Paths_* must include it also on the 'autogen-modules' field besides 'exposed-modules' and 'other-modules'. This specifies that the module does not come with the package and is generated on setup. Modules built with a custom Setup.hs script also go here to ensure that commands like sdist don't fail.
18 [no-autogen-pinfo] Packages using 'cabal-version: 2.0' and the autogenerated module PackageInfo_* must include it in 'autogen-modules' as well as 'exposed-modules' and 'other-modules'. This specifies that the module does not come with the package and is generated on setup. Modules built with a custom Setup.hs script also go here to ensure that commands like sdist don't fail.
19 [name-no-match] The filename './my.cabal' does not match package name (expected: 'AutogenModules.cabal')
20 Note: the public hackage server would reject this package.
21 Building source dist for AutogenModules-0.1...
23 Could not find module: MyLibHelperModule with any suffix: ["gc","chs","hsc","x","y","ly","cpphs","hs","lhs","hsig","lhsig"].
24 If the module is autogenerated it should be added to 'autogen-modules'.