- cabal-devel - Haskell.org

Re: [Hackage] #179: support GHC's main-is extension
by Hackage 21 Jun '11

21 Jun '11

#179: support GHC's main-is extension ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: reopened Priority: low | Milestone: _|_ Component: Cabal library | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ----------------------------+----------------------------------------------- Comment(by Evi1M4chine): Replying to [comment:23 cjs]:[[BR]] I always thought of it like this: * The `--main-is` for a build target doesn’t change. * Every build target should have its own separate build directory. * If `--main-is` ''is'' changed, that invalidates the object file that was previously set as main, causing it to get deleted. * As early as possible, it is checked that there can always be just one module that has a program entry point. Those rules would prevent the problem, no? P.S.: Aren’t universal binaries executables with two program entry points, where the correct one for the arch is chosen by the OS? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/179#comment:25> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #179: support GHC's main-is extension
by Hackage 21 Jun '11

21 Jun '11

#179: support GHC's main-is extension ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: reopened Priority: low | Milestone: _|_ Component: Cabal library | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ----------------------------+----------------------------------------------- Comment(by duncan): Thanks. Got it. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/179#comment:24> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #497: on package not found error: mention "cabal update"
by Hackage 21 Jun '11

21 Jun '11

#497: on package not found error: mention "cabal update" ----------------------------------+----------------------------------------- Reporter: Martijn | Owner: byorgey Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- Comment(by kowey): I've attached a patch which I think takes care of the "no available version" case, albeit not in a particularly principled way... -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/497#comment:5> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #179: support GHC's main-is extension
by Hackage 21 Jun '11

21 Jun '11

#179: support GHC's main-is extension ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: reopened Priority: low | Milestone: _|_ Component: Cabal library | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ----------------------------+----------------------------------------------- Comment(by cjs): Ah, sorry. Basically, different and incompatible object files are produced when you compile the same source with and without --main-is. Any object files compiled with --main-is cannot be linked into another program (that has its own main) because the two main functions will conflict at the link stage. Basically, the link stage doesn't know from main, it just links all the stuff together and depends on one (and only one) object file to have a program entry point (a "main") of some sort specified. This is a bit insidious because the object files go to the same location when compiled with or without --main-is. So if you do a clean build of some system with your --main-is set to one module, you will successfully link your final program. If you re-compile with the --main-is option reset, the GHC dependency checker (--make option) does not know that another module was previously compiled with --main-is, and when you hit the link stage you will get an error. Well, this is more or less how I remember it. If this still doesn't make sense, it's probably best to contact me via e-mail (cjs(a)cynic.net) and I can put together an example that demonstrates the problem more precisely, and give suggestions on how to have the build system deal with the issue (essentially, putting any object files compiled with --main-is in a separate object directory or just giving them different names). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/179#comment:23> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #179: support GHC's main-is extension
by Hackage 21 Jun '11

21 Jun '11

#179: support GHC's main-is extension ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: reopened Priority: low | Milestone: _|_ Component: Cabal library | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ----------------------------+----------------------------------------------- Comment(by duncan): Replying to [comment:21 cjs]: > Do note, if you start implementing this for GHC, that if Blah.hs doesn't export main and is linked into other programs the versions of this with and without the main function must be compiled separately. (A typical case for this is where the main function is a test framework.) Sorry, I don't think I see what you're getting at. Could you try explaining it slower :-) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/179#comment:22> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #179: support GHC's main-is extension
by Hackage 21 Jun '11

21 Jun '11

#179: support GHC's main-is extension ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: reopened Priority: low | Milestone: _|_ Component: Cabal library | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ----------------------------+----------------------------------------------- Comment(by cjs): That syntax works for me. Do note, if you start implementing this for GHC, that if Blah.hs doesn't export main and is linked into other programs the versions of this with and without the main function must be compiled separately. (A typical case for this is where the main function is a test framework.) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/179#comment:21> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #817: "main-is" misparsed in if/else, only by sdist
by Hackage 20 Jun '11

20 Jun '11

#817: "main-is" misparsed in if/else, only by sdist ----------------------------+----------------------------------------------- Reporter: jeffwheeler | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.0.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- An if/else block which sets the main-is value for an executable based on a flag is misparsed when running "cabal sdist" (it's parsed correctly when running "cabal install"). Upon failure, it appears that it's looking for a filename that is the two main-is options concatenated together. E.g., I get the error "cabal: HackerMain.hsMain.hs doesn't exist". The problematic bit looks like: if flag(hacking) main-is: HackerMain.hs else main-is: Main.hs My entire config can be found on hpaste: http://hpaste.org/44939/yicabal (problematic lines around 268). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/817> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

Re: [Hackage] #576: Show reverse dependencies
by Hackage 20 Jun '11

20 Jun '11

#576: Show reverse dependencies --------------------------------+------------------------------------------- Reporter: Lenny222 | Owner: Type: enhancement | Status: new Priority: normal | Milestone: HackageDB Component: hackageDB website | Version: 1.6.0.1 Severity: normal | Keywords: dependencies Difficulty: easy (<4 hours) | Ghcversion: Platform: | --------------------------------+------------------------------------------- Changes (by lelf): * cc: anton.nik@… (added) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/576#comment:8> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

patch applied (cabal): "Add a dash separator for pid in createTempDirectory and openBinaryTempFile too"
by Duncan Coutts 19 Jun '11

19 Jun '11

Wed May 18 19:16:58 PDT 2011 Jens Petersen <juhp(a)community.haskell.org> * Add a dash separator for pid in createTempDirectory and openBinaryTempFile too M ./cabal/Distribution/Compat/TempFile.hs -2 +2 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Update changelog for 1.10.2.0"
by Duncan Coutts 19 Jun '11

19 Jun '11

Sat Jun 18 12:07:48 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Update changelog for 1.10.2.0 M ./cabal/changelog +6 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0