April 2010 - cabal-devel

patch applied (cabal): Remove BSD4 from the list of known/suggested licenses
by Duncan Coutts 16 Apr '10

16 Apr '10

Thu Apr 15 21:05:38 PDT 2010 Duncan Coutts <duncan(a)haskell.org> * Remove BSD4 from the list of known/suggested licenses We do not ever want to suggest the use of the BSD4 license. This will fix a QA check message and the 'cabal init' command. This change should be safe to push into the stable 1.8 branch. M ./Distribution/License.hs -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): Add a VERSION_<package> define for each package in cabal_macros.h
by Duncan Coutts 15 Apr '10

15 Apr '10

Mon Mar 29 03:46:32 PDT 2010 Mathieu Boespflug <mboes(a)tweag.net> * Add a VERSION_<package> define for each package in cabal_macros.h The MIN_VERSION_<package> macros are useful to test whether we have at least a given version of a dependency, but we can't extract the actual version of dependency using this macro. This patch makes the version of each dependency available to the code of the cabal package, which can be useful when constructing global names in Template Haskell, for instance. M ./Distribution/Simple/Build/Macros.hs +2 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): Also check compiling C headers at configure-time
by Duncan Coutts 15 Apr '10

15 Apr '10

Wed Apr 14 23:36:57 PDT 2010 Duncan Coutts <duncan(a)haskell.org> * Also check compiling C headers at configure-time So we now both check if the headers can be pre-processed and separately if they can be compiled. If it fails the pre-processing check then it is usually (but not always) a missing header. If it fails to compile then it is definately borked, not missing. Error messages reflect this. M ./Distribution/Simple/Configure.hs -41 +61 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): better error messages for erroneous local C headers
by Duncan Coutts 15 Apr '10

15 Apr '10

Thu Apr 8 19:25:43 PDT 2010 mcallister.keegan(a)gmail.com * better error messages for erroneous local C headers Addresses the issue in tickets #532, #648. When the all-together test of C libraries and headers fails, use only the preprocessor to probe the headers individually. If they all check out, give a more equivocal error message and suggest -v3. M ./Distribution/Simple/Configure.hs -7 +21 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

Re: [Hackage] #532: libraries and include checks can be highly misleading
by Hackage 15 Apr '10

15 Apr '10

#532: libraries and include checks can be highly misleading ----------------------------+----------------------------------------------- Reporter: guest | Owner: kmcallister Type: defect | Status: closed Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.6.0.2 Severity: normal | Resolution: fixed Keywords: | Difficulty: easy (<4 hours) Ghcversion: | Platform: ----------------------------+----------------------------------------------- Changes (by duncan): * status: assigned => closed * resolution: => fixed Comment: Thanks! I've applied this and extended it so that we also check compiling headers. For example for a header with wrong C syntax we get: {{{ Configuring foo-1.0... setup: Bad header file: error.h The header file contains a compile error. You can re-run configure with the verbosity flag -v3 to see the error messages from the C compiler. }}} Where as if the header has a pre-processing error (eg `#include "missing.h"`) then we get: {{{ Configuring foo-1.0... setup: Missing dependency on a foreign library: * Missing (or bad) header file: error.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. If the header file does exist, it may contain errors that are caught by the C compiler at the preprocessing stage. In this case you can re-run configure with the verbosity flag -v3 to see the error messages. }}} Patches applied: {{{ Fri Apr 9 03:25:43 BST 2010 mcallister.keegan(a)gmail.com * better error messages for erroneous local C headers Addresses the issue in tickets #532, #648. When the all-together test of C libraries and headers fails, use only the preprocessor to probe the headers individually. If they all check out, give a more equivocal error message and suggest -v3. Thu Apr 15 07:24:01 BST 2010 Duncan Coutts <duncan(a)haskell.org> * Also check compiling C headers at configure-time So we now both check if the headers can be pre-processed and separately if they can be compiled. If it fails the pre-processing check then it is usually (but not always) a missing header. If it fails to compile then it is definately borked, not missing. Error messages reflect this. }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/532#comment:7> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[SPAM] patch applied (cabal): document all the language extensions
by Duncan Coutts 13 Apr '10

13 Apr '10

Thu Apr 8 23:05:59 PDT 2010 mcallister.keegan(a)gmail.com * document all the language extensions Resolves ticket #344. M ./Language/Haskell/Extension.hs -7 +191 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): Various minor improvements to c2hs support
by Duncan Coutts 13 Apr '10

13 Apr '10

Tue Apr 13 01:32:52 PDT 2010 Duncan Coutts <duncan(a)haskell.org> * Various minor improvements to c2hs support - ticket #327: require c2hs version 0.15 as minimum - ticket #536: pass c2hs include dirs of dependent packages - ticket #537: pass c2hs location of gcc -E M ./Distribution/Simple/PreProcess.hs -12 +32 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): Get ghc, hsc2hs and cpphs programs more robustly in preprocessing
by Duncan Coutts 13 Apr '10

13 Apr '10

Sun Apr 11 19:36:42 PDT 2010 Duncan Coutts <duncan(a)haskell.org> * Get ghc, hsc2hs and cpphs programs more robustly in preprocessing Avoid pattern match failure in obscure circumstances Should fix ticket #383 M ./Distribution/Simple/PreProcess.hs -53 +61 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): Move .hs-boot file pre-processor hack to a more sensible place
by Duncan Coutts 13 Apr '10

13 Apr '10

Sun Apr 11 18:51:27 PDT 2010 Duncan Coutts <duncan(a)haskell.org> * Move .hs-boot file pre-processor hack to a more sensible place M ./Distribution/Simple/PreProcess.hs -20 +30 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

problems getting cabal-install to work on CentOS
by Chris Dornan 13 Apr '10

13 Apr '10

Hi, I sent the message below out to libraries and then haskell-café before I thought to try, or realised that there must be, a Cabal development list (which I have now joined). Basically I am trying to get the latest cabal-install to work with GHC-6.12.1 on CentOS 5 and it is giving me an ExitFailure 127 when it tries to configure the app with Cabal. Note that I can manually configure, build and install the app myself without any problemI can even down load the cabal tarbal, cd into the root directory and type cabal install and it will work (provided it doesnt have to download and install any dependent packages). I dont know what is going wrong but, unless somebody knows what is failing, to make progress it looks as if I need to add some instrumentation around the code that is generating the error. Can anybody point me in the right direction? If somebody has encountered this before, or knows what is likely to be going on, or of Cabal debug infrastructure I can call on, or the part of the source code that I can instrument, I would be very grateful! Cheers, Chris I am trying to install cabal-install 0.8.2 with GHC 6.12.1 on a CentOS 5.2 system and am running up against a ExitFailure 127 error. I can download the package and run cabal install inside the package directory and all will be fine, but if I let cabal download and install the package cabal runs into problems as soon as it tries to configure. For example, if I try cabal install permutation --verbose=3 it finishes like this: link: done *** Deleting temp files: Deleting: /tmp/ghc1324_0/ghc1324_0.lpp *** Deleting temp dirs: Deleting: /tmp/ghc1324_0 /tmp/permutation-0.4.132758/permutation-0.4.1/dist/setup/setup configure --verbose=3 --ghc --prefix=/home/chris/.cabal --user --constraint=base ==3.0.3.2 --constraint=ghc-prim ==0.2.0.0 cabal: Error: some packages failed to install: permutation-0.4.1 failed during the configure step. The exception was: ExitFailure 127 I have tried the same exercise with GHC 6.10.4 with cabal-install 0.8.0 the same results. I have downloaded the Cabal sources to try and add some instrumentation to find out what is going wrong but have yet to succeed. Does anybody have any suggestions? Is there an easier way of getting cabal-install working on CentOS? Any help much appreciated!

1 0