April 2007 - cabal-devel

HEADS UP: Windows Vista users
by Simon Marlow 12 Apr '07

12 Apr '07

I've discovered a gotcha that happens when trying to use Cabal on Windows Vista. If you compile Setup.lhs to a binary (as I often do), with something like 'ghc --make Setup', and then try to run it, you'll get something like this: $ ./Setup configure Setup.exe: Permission denied This is due to a highly dubious security "feature" in Vista whereby it detects that you might be trying to run an installer-type program and refuses to execute the binary without elevated permissions. The idea is that ordinary users won't be confused when their installer fails partway through due to insufficient permissions. Unfortunately this works by matching on the name of the binary(!!!!), so names like "setup", "install" etc. are affected (there isn't a complete list, apparently). Other casualties are: * cabal-setup (compiles Setup.hs to setup.exe) * The GHC build system, which now uses Cabal * 'make install', which runs /usr/bin/install.exe More details in this MSDN thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1021146&SiteID=1 and this Cygwin thread: http://www.cygwin.com/ml/cygwin/2006-12/msg00518.html Fortunately you can turn off the behaviour: Start->Run->secpol.msc, then Security Settings -> Local Policies -> Security Options ! UAC: Detect application installations and prompt for elevation. It appears you need to reboot for the change to take effect. The right workaround is to add a manifest to the binary asking for no security elevation, apparently this is quite easy. We'll need to get GHC to do this for every binary it generates in the future. For now, I'll put a note in the building guide and FAQ, and make a ticket for GHC 6.6.2 to do the manifest thing. Cheers, Simon

1 0

Setup sdist broken on Windows
by Neil Mitchell 10 Apr '07

10 Apr '07

Hi, On Windows, taking the filepath library: Building source dist for filepath-1.0... copy System\FilePath.hs to dist\src\filepath-1.0\.\System\FilePath.hs copy System\FilePath\Posix.hs to dist\src\filepath-1.0\.\System\FilePath\Posix.h s copy System\FilePath\Windows.hs to dist\src\filepath-1.0\.\System\FilePath\Windo ws.hs copy System\FilePath\Internal.hs to dist\src\filepath-1.0\System\FilePath\Intern al.hs copy Setup.hs to dist\src\filepath-1.0\Setup.hs copy filepath.cabal to dist\src\filepath-1.0\filepath.cabal D:\bin\tar.exe -C dist\src -czf dist\filepath-1.0.tar.gz filepath-1.0 D:\bin\tar.exe: Cannot use compressed or remote archives D:\bin\tar.exe: Error is not recoverable: exiting now Setup: source tarball creation failed! Tar exited with status 2 Using Cabal from about 2 minutes ago. Any idea what is wrong? Thanks Neil

2 1

Building Projects under mingw that use c2hs [apologies for repost; archive seemed to scrub text portion, see archive for attached file]
by Alexander McPhail 07 Apr '07

07 Apr '07

Hi, I have been trying to build a Cabal package that uses c2hs under mingw and have run into some problems. 1) c2hs needed its own options because it has to pass a flag to its invocation of the CPP. I have already submitted this patch. (I also noticed a request for cppOptions in the Cabal.cabal file, so I added that) 2) When c2hs generates the foreign import ccall unsafe "path/to/include.h function" :: Type it doesn't insert the appropriate number of path separators for windows ( i.e. \\ not \) I have this patch sitting in my copy of c2hs. But what I did is really ugly: at around line 567 (process :: FilePath -> FilePath -> CST s ()) I inserted: > outFName' <- getSwitch outputSB > -- on windows the path separator needs to be "\\" not "\" > let outFName = replaceFileSeparator outFName' where replaceFileSeparator is defined as: > replaceFileSeparator :: String -> String > replaceFileSeparator [] = [] > replaceFileSeparator (x:xs) > | x == '\\' = "\\\\" ++ (replaceFileSeparator xs) > | otherwise = x : (replaceFileSeparator xs) this fixes the problem but stinks. 3) when compiling my c2hs generated .hs file, the c2hs generated .h file is not being found. $ ./Setup.lhs -v build Reading parameters from D:\Apps\MSYS\1.0\local\src\mingw-c2hs-cabal-test\cabal-root\mingw- c2hs-cabal-test.buildinfo Preprocessing library Mingw-c2hs-cabal-test-0.0.1... D:\Apps\MSYS\1.0\local\bin\c2hs.exe -C -D__GLASGOW_HASKELL__=606 -C -I..\include --cppopts=-I../include --include=src -o src\Cabal\MingwTest.hs src\Cabal\MingwTest.chs D:\Apps\MSYS\1.0\local\bin\c2hs.exe -C -D__GLASGOW_HASKELL__=606 -C -I..\include --cppopts=-I../include --include=src -o src\Cabal\MingwTest2.hs src\Cabal\MingwTest2.chs Building Mingw-c2hs-cabal-test-0.0.1... d:\Apps\ghc\ghc- 6.6\bin\ghc.exe -package-name Mingw-c2hs-cabal-test-0.0.1--make -hide-all-packages -i -idist\build\autogen -i. -isrc -I..\include -#include "test.h" -odir dist\build -hidir dist\build -package base-2.0 -O -package haskell98 -fglasgow-exts -fffi Cabal.MingwTest Cabal.MingwTest2C2HS [1 of 3] Compiling C2HS ( src/C2HS.hs, dist\build/C2HS.o ) [2 of 3] Compiling Cabal.MingwTest ( src/Cabal/MingwTest.hs, dist\build/Cabal/MingwTest.o ) C:\DOCUME~1\vivian\LOCALS~1\Temp\ghc31772_0\ghc31772_0.hc:6:33: src\Cabal\MingwTest.h: No such file or directory I have attached a set of files that will generate the errors I have mentioned on mingw. Cheers, Vivian

1 0

Building Projects under mingw that use c2hs
by Alexander McPhail 07 Apr '07

07 Apr '07

Hi, I have been trying to build a Cabal package that uses c2hs under mingw and have run into some problems. 1) c2hs needed its own options because it has to pass a flag to its invocation of the CPP. I have already submitted this patch. (I also noticed a request for cppOptions in the Cabal.cabal file, so I added that) 2) When c2hs generates the foreign import ccall unsafe "path/to/include.h function" :: Type it doesn't insert the appropriate number of path separators for windows (i.e. \\ not \) I have this patch sitting in my copy of c2hs. But what I did is really ugly: at around line 567 (process :: FilePath -> FilePath -> CST s ()) I inserted: > outFName' <- getSwitch outputSB > -- on windows the path separator needs to be "\\" not "\" > let outFName = replaceFileSeparator outFName' where replaceFileSeparator is defined as: > replaceFileSeparator :: String -> String > replaceFileSeparator [] = [] > replaceFileSeparator (x:xs) > | x == '\\' = "\\\\" ++ (replaceFileSeparator xs) > | otherwise = x : (replaceFileSeparator xs) this fixes the problem but stinks. 3) when compiling my c2hs generated .hs file, the c2hs generated .h file is not being found. $ ./Setup.lhs -v build Reading parameters from D:\Apps\MSYS\1.0\local\src\mingw-c2hs-cabal-test\cabal-root\mingw- c2hs-cabal-test.buildinfo Preprocessing library Mingw-c2hs-cabal-test-0.0.1... D:\Apps\MSYS\1.0\local\bin\c2hs.exe -C -D__GLASGOW_HASKELL__=606 -C -I..\include --cppopts=-I../include --include=src -o src\Cabal\MingwTest.hs src\Cabal\MingwTest.chs D:\Apps\MSYS\1.0\local\bin\c2hs.exe -C -D__GLASGOW_HASKELL__=606 -C -I..\include --cppopts=-I../include --include=src -o src\Cabal\MingwTest2.hs src\Cabal\MingwTest2.chs Building Mingw-c2hs-cabal-test-0.0.1... d:\Apps\ghc\ghc-6.6\bin\ghc.exe -package-name Mingw-c2hs-cabal-test-0.0.1--make -hide-all-packages -i -idist\build\autogen -i. -isrc -I..\include -#include "test.h" -odir dist\build -hidir dist\build -package base-2.0 -O -package haskell98 -fglasgow-exts -fffi Cabal.MingwTest Cabal.MingwTest2C2HS [1 of 3] Compiling C2HS ( src/C2HS.hs, dist\build/C2HS.o ) [2 of 3] Compiling Cabal.MingwTest ( src/Cabal/MingwTest.hs, dist\build/Cabal/MingwTest.o ) C:\DOCUME~1\vivian\LOCALS~1\Temp\ghc31772_0\ghc31772_0.hc:6:33: src\Cabal\MingwTest.h: No such file or directory I have attached a set of files that will generate the errors I have mentioned on mingw. Cheers, Vivian

1 0

Building individual programs
by allan 06 Apr '07

06 Apr '07

Dear all I have a cabal package which defines in the cabal package several programs to be built such as: Executable: prog1 Main-is: examples/Prog1.hs Ghc-options: -Wall Executable: prog2 Main-is: examples/Prog2.hs Ghc-options: -Wall It's actually a library and the individual programs are a bunch of examples. When I work on one of these individually it's mildly annoying that runhaskell Setup.hs build builds all of them. I'd quite like to be able to do something like: runhaskell Setup.hs build prog1 or even just runhaskell Setup.hs prog1 to build only the first example. I know about the "Buildable" field in the cabal file, but I was kind of hoping there was a way to do this such that the cabal file doesn't need to be continually modified (and runhaskell Setup.hs configure --..... re-run). So is there a (standard) way to do this? If not, I suppose the best way to do it would be in the Setup.hs file, ie could do something like: processArgs :: [ String ] -> IO () processArgs [ "prog1" ] = <Something to build prog1 with all the configuration information> processArgs _ = defaultMainWithHooks myHooks if this is the best way, what should I have in the <Something .. > bit? regards allan

1 0