December 2009 - cabal-devel

[Hackage] #552: Cabal fails because header file is missing. But in fact the header file is erroneous.
by Hackage 22 Dec '09

22 Dec '09

#552: Cabal fails because header file is missing. But in fact the header file is erroneous. ---------------------------------+------------------------------------------ Reporter: mgross | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: Mac OS | ---------------------------------+------------------------------------------ When trying to install HERA 0.2 the {{{ runhaskell Setup.hs configure }}} command fails with: {{{ Setup.hs: Missing dependency on a foreign library: * Missing header file: hsmpfr.h This problem can usually be solved by installing the system package that provides this library (you may need the "-dev" version). If the library is already installed but in a non-standard location then you can use the flags --extra-include-dirs= and --extra-lib-dirs= to specify where it is. }}} But in fact the header file is present. The real problem is an include in the header file. The include {{{ #include <malloc.h> }}} fails on Mac OS systems. It would be better if Cabal would report the compile error. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/552> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #463: Do not work in Windows Vista
by Hackage 22 Dec '09

22 Dec '09

#463: Do not work in Windows Vista ---------------------------------+------------------------------------------ Reporter: Tonal | Owner: Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.6 Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.10.1 Platform: | ---------------------------------+------------------------------------------ My Environment: Os: Windows Vista Home Ru + sp1 User name: Леново ghc 6.10.1 (Cabal-1.6.0.1 from installation) cabal-install-0.6.0 Other lib: HTTP-3001.1.5 zlib-0.5.0.0 Cabal-install compile and link. Bat all commands not work. For example: {{{ C:\Lang\Haskell\ghc>cabal list Config file C:\Users\Леново\AppData\Roaming\cabal\config not found. Writing default configuration to C:\Users\Леново\AppData\Roaming\cabal\config cabal: CreateDirectory: does not exist (!8AB5<5 =5 C405BAO =09B8 C:070==K9 ?CBL.) }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/463> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

[Hackage] #445: Simple builds ignore .buildinfo
by Hackage 22 Dec '09

22 Dec '09

#445: Simple builds ignore .buildinfo ----------------------------+----------------------------------------------- Reporter: awick | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ----------------------------+----------------------------------------------- It would be convenient if Simple builds would look for buildinfo files, instead of just ignoring them. It's sometimes convenient to have the configure script run as a separate phase (for example, when you're configuring a bunch of separate cabal packages) instead of re-running the same configure tests every time, and this would help. There's an obvious workaround (setting the type to 'Configure' and then adding an empty 'configure' script), but this is tedious. I've attached a simple example. The .buildinfo file tells Cabal to build Test2 in addition to Test1. If you set the type to Simple, it only builds Test1. If you set it to 'Configure', it runs the empty configure script and then builds both Test1 and Test2. It'd be nicer if 'Simple' caused both Test1 and Test2 to be built, as well. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/445> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #429: Strange error that seems related to repos field in config
by Hackage 22 Dec '09

22 Dec '09

#429: Strange error that seems related to repos field in config ----------------------------+----------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.10.1 Platform: | ----------------------------+----------------------------------------------- I'm reporting this although I don't really know what the problem is. I installed cabal-install using GHC 6.10.1. When I tried to use it, it complained that the it couldn't open the file 'Ê', or some other strange, seemingly random, one-character long file name. An strace revealed that just before trying to open the file it reads the repos: field from the config file in ~/.cabal. That field was set to "hackage.haskell.org:http://hackage.haskell.org/packages/archive". I tried removing the initial "hackage.haskell.org:", and them cabal-install works. Not sure what this is, but I couldn't find something about it in the bug tracker after a quick search. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/429> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #427: how to access temporary build-files/logs?
by Hackage 22 Dec '09

22 Dec '09

#427: how to access temporary build-files/logs? ----------------------------+----------------------------------------------- Reporter: claus | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ----------------------------+----------------------------------------------- when trying to debug an installation failure, it would be most useful to be able to keep the temporary build files (similar to ghc's -keep* options). Apart from being able to look at things like `config.log`, it would also allow to experiment with patched commands from the verbose build log (which needs the temporary files still present). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/427> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 9

Re: [Hackage] #147: Replace Extension type with (newtyped?) String
by Hackage 22 Dec '09

22 Dec '09

#147: Replace Extension type with (newtyped?) String ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: _|_ Component: Cabal library | Version: 1.1.6 Severity: normal | Resolution: fixed Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ----------------------------+----------------------------------------------- Changes (by duncan): * status: new => closed * resolution: => fixed Comment: I'm closing this. The original problem is fixed though not via the suggested solution. That is to say that Cabal does now let you list extensions in the .cabal file that Cabal does not know about and if ghc supports them then it'll work. However we still want to maintain a registry of known semi-standardised extensions. Then the choice between using a newtyped String and an enumeration with an `UnknownExtension String` case is a more detailed question of API and implementation. If anyone feels strongly about the latter then they should present their arguments (and patches) in this ticket or a new ticket. Alternatively if anyone feels strongly that Cabal should not maintain the registry of known semi-standardised extensions, then that's a discussion we should probably hold on the mailing list. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/147#comment:3> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #110: cabal should detect when a new version of a library is installed
by Hackage 22 Dec '09

22 Dec '09

#110: cabal should detect when a new version of a library is installed ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Cabal-2.0 Component: Cabal library | Version: 1.1.6 Severity: normal | Resolution: fixed Keywords: | Difficulty: hard (< 1 day) Ghcversion: 6.6 | Platform: ----------------------------+----------------------------------------------- Changes (by duncan): * status: new => closed * resolution: => fixed Comment: For ghc this is now done by ghc --make itself (I think since 6.8 or 6.10). The more general problem is the same as always, the lack of a proper dep system #15. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/110#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #216: need a way to specify the foreign libraries a package depends on
by Hackage 22 Dec '09

22 Dec '09

#216: need a way to specify the foreign libraries a package depends on ----------------------------------+----------------------------------------- Reporter: ross(a)soi.city.ac.uk | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: major | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: Linux | ----------------------------------+----------------------------------------- Package descriptions allow one to specify which Haskell libraries a package depends on, but foreign ones. Designing something that can be used with native package managers is complicated because many of them alter the upstream library names in unpredictable ways. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/216> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 11

[Hackage] #545: Uninformative error message when cabal-install fails on WinXP
by Hackage 22 Dec '09

22 Dec '09

#545: Uninformative error message when cabal-install fails on WinXP ---------------------------------+------------------------------------------ Reporter: abayley | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ "cabal install binary" fails on my WinXP machine with this error: Resolving dependencies... Downloading binary-0.4.4... cabal: Error: some packages failed to install: binary-0.4.4 failed while downloading the package. Suspect it's related to proxy configuration, but the error message could be more informative. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/545> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #542: installing cabal-install refers to editing nonexistent file $HOME/.cabal/config
by Hackage 22 Dec '09

22 Dec '09

#542: installing cabal-install refers to editing nonexistent file $HOME/.cabal/config ---------------------------------+------------------------------------------ Reporter: nr | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: minor | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ {{{cabal --help}}} invites me to edit a file that doesn't exist, and I can't easily find documentation for the file: {{{ : nr@homedog 5520 ; cabal --help This program is the command line interface to the Haskell Cabal infrastructure. ... You can edit the cabal configuration file to set defaults: /home/nr/.cabal/config : nr@homedog 5521 ; ls -l /home/nr/.cabal/config ls: cannot access /home/nr/.cabal/config: No such file or directory }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/542> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3