Esa Ilari Vuokko wrote:
> Is the right fix to make Cabal unquote the fields it
> receives from ghc-pkg, or is there some more complex
> problem lurking around?
Attached patch uses existing parsers to handle ghc-pkg
output. It still ignores multiple values, as it used to
before, as well. I have n
On Wed, Aug 08, 2007 at 04:19:29PM +0100, Simon Marlow wrote:
>
> I've just made GHC's Cabal into a branch.
FWIW I think this is a mistake. It'll make changing Cabal as part of
changes to the larger system harder, and increases the global amount of
effort necessary.
Also, I think Cabal patches w
This is caused by a bug in Cabal. I have submitted a patch to cabal-devel
already which fixes this! Hopefully it will be accepted soon.
On Thu, 9 Aug 2007, Ian Lynagh wrote:
Building base gives
Data/Generics.hs:28:1: lexical error at character 'i'
and if I try with the build rule rather t
On Wed, Aug 08, 2007 at 10:27:07AM +1000, Manuel M T Chakravarty wrote:
> /opt/local/bin/ghc -H64m -Onot -fasm -istage1/utils
> -istage1/basicTypes -istage1/types -istage1/hsSyn
> -istage1/prelude -istage1/rename -istage1/typecheck
> -istage1/deSugar -istage1/coreSyn -istage1/vectorise
>
Hi,
I think some recent change might have brought following
problem up. installed-pkg-config has some fields escaped
when they have spaces (or commas as Thomas showed me in
irc.) The token is quoted using Prelude.Show. In case of
haddock-interfaces, Cabal actually asks this information
back whe
Extensions do not work with ghc 6.7. This patch fixes it:
http://magnus.smartelectronix.com/temp/cabal-fix.darcs-patch
Duncan knows what this is.
Cheers,
Magnus Jonsson
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mail
Manuel M T Chakravarty wrote:
An automated system would be cool, but it'd require some effort to set
up. In the meantime, we should probably go with SimonM's proposal and
just make GHC use a subset-branch of the main Cabal repo. Pulling
changes over into GHC's Cabal branch would be a manual
On Wed, 2007-08-08 at 12:06 +0100, Duncan Coutts wrote:
> On Wed, 2007-08-08 at 09:22 +0100, Simon Marlow wrote:
> > Duncan Coutts wrote:
> > > I am trying to understand the reason we have so many --dir flags to
> > > configure. I'd prefer to remove what appear to be duplicates and add
> > > some m
On Wed, 2007-08-08 at 09:22 +0100, Simon Marlow wrote:
> Duncan Coutts wrote:
> > I am trying to understand the reason we have so many --dir flags to
> > configure. I'd prefer to remove what appear to be duplicates and add
> > some more dir overrides for specific file types (like docs).
> >
> > We
Simon Marlow wrote:
> Esa Ilari Vuokko wrote:
>> Issue 1:
>> Cabal puts (at least) docs under Program Files\Common Files - this
>> separates docs from other parts of the program by logical placing,
>
> Not quite true: for an executable, on Windows, docs currently go by
> default into $prefix\Hask
Duncan Coutts wrote:
I am trying to understand the reason we have so many --dir flags to
configure. I'd prefer to remove what appear to be duplicates and add
some more dir overrides for specific file types (like docs).
We currently have:
--libdir= and --libsubdir=
--datadir= and --datasubdir=
Esa Ilari Vuokko wrote:
Hi,
I decided to try to build a cabal -> wix converter, cabal2wix, to make
it easier to generate Windows installers for cabal-packages. My main
target is ghc-compiled libraries. There are few issues I've ran into
and I'd appreciate any comments on them.
I'll try to pub
12 matches
Mail list logo
