Has anybody tried to upgrade Cabal on HP (Win 7)

newer
The functional-object style seems...

older
Re: [Haskell-cafe] What is Haskell...

Daniel Kahlenberg

18 Jun 2010 18 Jun '10

10:48 a.m.

Hello, I recently installed HP 2010.1.0.0 within Windows 7 and wanted to upgrade the Cabal package to 1.8.0.6 today, sadly I got stuck on a failure building the "directory" package. So I tried to isolate the messages a bit and gave the following a try in a ghci session (1st time only with path to cygwin binaries/2nd time only with path to msys binaries added on my path variable, for both times I append the logging output): Prelude System.Cmd>

...

rawSystem "cabal" ["upgrade", "--constraint=base==4.*", "directory", "-v3", "--user", "--build-log=d:/temp/log/build-$$pkgid-$$compiler.log"]

Maybe we can find the cause?! Greetz Daniel

Attachments:

build-directory-1.0.1.1-ghc-6.12.1-cygwin.log (text/plain — 13.1 KB)
build-directory-1.0.1.1-ghc-6.12.1-msys.log (text/plain — 12.5 KB)

Show replies by date

JP Moresmau

18 Jun 18 Jun

11:07 a.m.

On Fri, Jun 18, 2010 at 4:48 PM, Daniel Kahlenberg < d.kahlenberg@googlemail.com> wrote:

...

Hello,

I recently installed HP 2010.1.0.0 within Windows 7 and wanted to upgrade the Cabal package to 1.8.0.6 today, sadly I got stuck on a failure building the "directory" package.

So I tried to isolate the messages a bit and gave the following a try in a ghci session (1st time only with path to cygwin binaries/2nd time only with path to msys binaries added on my path variable, for both times I append the logging output):

Prelude System.Cmd>

...
rawSystem "cabal" ["upgrade", "--constraint=base==4.*", "directory", "-v3", "--user", "--build-log=d:/temp/log/build-$$pkgid-$$compiler.log"]

Maybe we can find the cause?!

Greetz Daniel

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

I see on the gcc command line: -IC:\\Program Files (x86)\\Haskell Platform\\2010.1.0.0/include On my machine, HsFFI.h is in lib/include, so maybe try with --extra-include-dirs=-IC:\\Program Files (x86)\\Haskell Platform\\2010.1.0.0\\lib\\include I also ran into problems with the directory package on windows, that I got around by making sure every thing was installed with --global -- JP Moresmau http://jpmoresmau.blogspot.com/

Daniel Kahlenberg

11:53 a.m.

On 18.06.2010 17:07, JP Moresmau wrote:

...

On Fri, Jun 18, 2010 at 4:48 PM, Daniel Kahlenberg mailto:d.kahlenberg@googlemail.com> wrote:

...

Prelude System.Cmd> > rawSystem "cabal" ["upgrade", "--constraint=base==4.*", "directory", > "-v3", "--user", > "--build-log=d:/temp/log/build-$$pkgid-$$compiler.log"]

I see on the gcc command line:

-IC:\\Program Files (x86)\\Haskell Platform\\2010.1.0.0/include

So, is it a bug in the cabal file?? Proposing

...

include-dirs: include had to be something like: if os(windows) { include-dirs: lib/include } else { include-dirs: include }

On my machine, HsFFI.h is in lib/include, so maybe try with --extra-include-dirs=-IC:\\Program Files (x86)\\Haskell Platform\\2010.1.0.0\\lib\\include

Cool! To be more exact in my case it was: --extra-include-dirs=C:\\Program Files (x86)\\Haskell Platform\\2010.1.0.0\\lib\\include

...

I also ran into problems with the directory package on windows, that I got around by making sure every thing was installed with --global

You're right. I guess, this is intended and won't be changed? Because directory is kind of core package, right? Installing it in the user package data file would complicate things more than it would help to keep things on different access levels? As a general question this means, certain packages won't ever be installable without special access rights on a standard system, on the other side one could simply install the HP and global packages to a writable folder (against the proposed one on a Windows system), although my experiences didn't left me very optimistic about non-standard solutions in this case. On the other hand, one could upgrade GHC manually or wait for the next HP, where the above mentioned objections counted too, though seem weaker. Cheers Daniel

Daniel Kahlenberg

12:12 p.m.

On 18.06.2010 17:07, JP Moresmau wrote:

...

got around by making sure every thing was installed with --global

I forgot using the --global flag to be complete, so here is the full command in a ghci session (account with full access rights, msys tools on path) again: Prelude System.Cmd>

...

rawSystem "cabal" ["upgrade", "directory", "-v3", "--build-log=d:/temp/ log/build-$$pkgid-$$compiler-msys.log", "--extra-include-dirs=C:\\Progra m Files (x86)\\Haskell Platform\\2010.1.0.0\\lib\\include", "--global"]

Otherwise things will be installed in privileged users package file. Daniel

Duncan Coutts

4:56 p.m.

On 18 June 2010 15:48, Daniel Kahlenberg wrote:

...

Hello,

I recently installed HP 2010.1.0.0 within Windows 7 and wanted to upgrade the Cabal package to 1.8.0.6 today, sadly I got stuck on a failure building the "directory" package.

So I tried to isolate the messages a bit and gave the following a try in a ghci session (1st time only with path to cygwin binaries/2nd time only with path to msys binaries added on my path variable, for both times I append the logging output):

Prelude System.Cmd>

...
rawSystem "cabal" ["upgrade", "--constraint=base==4.*", "directory", "-v3", "--user", "--build-log=d:/temp/log/build-$$pkgid-$$compiler.log"]

Maybe we can find the cause?!

I should note that in the current development version of the 'cabal' program, I have disabled the 'upgrade' command entirely. Your current problem is a good example of why I have done this. By using 'cabal install Cabal' rather than 'cabal upgrade Cabal' you would not have been led up the blind alley of trying to install a new version of the directory package. The fact is that you do not want to install a new version of the directory package. You want to use the version you have already got. The root problem is that 'cabal upgrade' is misleading. It does not do what people expect. It currently means "install the latest version of this package, and the latest version of all of its dependencies". That is not useful because you do not want to install the latest version of core packages like directory. The behaviour of 'cabal install' is what you want, it means "install the latest version of this package, but try to use existing installed versions of all dependencies". Duncan

5452

Age (days ago)

5452

Last active (days ago)

List overview

Download

4 comments

3 participants

participants (3)

Daniel Kahlenberg
Duncan Coutts
JP Moresmau